I understand complete ht-logic with scanning like Apache has is undesired overkill. But just for authentication something like a structured file that lives in the site root and holds the relative paths and user/pass combo's could work - or so it seems with my limited knowledge on the subject.by mattice - Migration from Other Servers
Thanks for the heads up. Automagic rebuilding of the configs it is then,,. Is there are specific reason the authors did not code any logic for this? I assume speed - but it would be nice to have something (imo) elementary as this in Nginx. We started out using Nginx as a proxy for static files in front of Apache but slowly are migrating everything. Hence why the question came up - it is tby mattice - Migration from Other Servers
Hello, In Apache users can protect their own directories as they see fit. They just upload a .htaccess and .htpasswd and it works. I know how to protect a directory in the configuration file of Nginx, but is it possible (one way or the other) to have something similar as Apache does? So my users can protect / unprotect their directories through FTP - without me having to change the configurby mattice - Migration from Other Servers