Support

Thank you for your report! It's much appreciated.

You're right, there's a gap in the JavaScript file CheckTempAndLogDirectories.js for this feature; it lacks the anti-CSRF token when building the endpoint URL used to contact your server. It was the one place I forgot to do that when I was improving the way anti-CSRF is being handled in our JavaScript. I also noticed that the integration test was focused on testing that the backend code works, not that the frontend code generates the correct URL. I have now addressed that testing gap by adding a test based on browser automation to ensure this never happens again. As I've always said, no amount of tests will make a product bug-free; we can only test the issues we have seen and can think about, and this kind of issue was neither to me. 

Since this is a minor feature I am not going to make a new release right away. The fix will make it into the next release which is scheduled for late October to early November.