I have an operational NGINX server with e few dozen location {}
definitions
When a connection is made from an internal network towards the server
the client browser gets all the pages. Now I like to add external
access, but I need to require basic authentication. Can this be done
without duplication of these few dozen location {} definitions or ???
On Fri, Feb 05, 2010 at 11:23:47PM +0100, Paul S. wrote:
I have an operational NGINX server with e few dozen location {}
definitions
When a connection is made from an internal network towards the server
the client browser gets all the pages. Now I like to add external
access, but I need to require basic authentication. Can this be done
without duplication of these few dozen location {} definitions or ???
I have an operational NGINX server with e few dozen location {}
definitions
When a connection is made from an internal network towards the server
the client browser gets all the pages. Now I like to add external
access, but I need to require basic authentication. Can this be done
without duplication of these few dozen location {} definitions or ???
I think creative use of the “include” directive can eliminate the
duplication for you. Keep the config for locations in separate files,
and then include them as appropriate. You can also have an include for
authentication. http://wiki.nginx.org/NginxHttpMainModule#include
–
RPM
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.