I’m wondering if I need to perform a “service nginx restart”, if I do
any changes to htpasswd file:
location / {
auth_basic “closed site”;
auth_basic_user_file htpasswd;
}
I noticed that sometimes it works without reloading the service.
On Wed, Apr 25, 2012 at 12:59:50PM -0400, TECK wrote:
Hi,
I’m wondering if I need to perform a “service nginx restart”, if I do
any changes to htpasswd file:
location / {
auth_basic “closed site”;
auth_basic_user_file htpasswd;
}
I noticed that sometimes it works without reloading the service.
The htpasswd file is looked up at runtime, no reload/restart
needed after it’s change.
Sorry to repeat myself Maxim. The file is looked at startup so if I add
a new user or edit an existing password, it will not require a service
restart?
On Thu, Apr 26, 2012 at 10:10:16AM -0400, TECK wrote:
Sorry to repeat myself Maxim. The file is looked at startup so if I add
a new user or edit an existing password, it will not require a service
restart?
The file is looked at runtime, i.e. when request comes and nginx
checks authentication/authorization for a particular request.
There is no need to reload/restart nginx if you add users or
change passwords of existing users.
Maxim D.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.