Wow this looks very nice, and so lightweight! Looking forward to trying a core integration. Many thanks!
Now for the issue - I wonder if we could ease integration by auto-generating a .htaccess entry for all storages (or through an upgrade wizard task & CLI command or so)?
It's probably hard to detect whether nginx is used, to be able to emit a warning. Maybe something for the maintenance check backend module.
Also when a htaccess file already exists, editing the file may not be wanted. And single subdir htaccess files of course clutter configuration.
Well. Maybe at the least this issue could help to think about an "integrity" maintenance check that checks all storages whether the middleware listens to that directory? Without introducing DOS/information disclosure attacks of course, so probably gated with a backend login.
(Feel free to close/discard the issue when it has been addressed or discarded already, no worries)
Wow this looks very nice, and so lightweight! Looking forward to trying a core integration. Many thanks!
Now for the issue - I wonder if we could ease integration by auto-generating a .htaccess entry for all storages (or through an upgrade wizard task & CLI command or so)?
It's probably hard to detect whether nginx is used, to be able to emit a warning. Maybe something for the maintenance check backend module.
Also when a htaccess file already exists, editing the file may not be wanted. And single subdir htaccess files of course clutter configuration.
Well. Maybe at the least this issue could help to think about an "integrity" maintenance check that checks all storages whether the middleware listens to that directory? Without introducing DOS/information disclosure attacks of course, so probably gated with a backend login.
(Feel free to close/discard the issue when it has been addressed or discarded already, no worries)