RFC: "global" location functionality

Michael Shadle mike503 at gmail.com
Sun Jul 19 16:22:42 MSD 2009

right now any time you have to protect a location, you have to put in
a second location block for php. You've said yourself this isn't a
highly suggested method.

I've also run into issues where my expires headers can sometimes
conflict with things...

would there be some way to implement some sort of global location
block method? perhaps it gets applied -after- the normal location
logic, and has a new marker?

that way we could safely apply things like expires headers or a php
block -after- any sort of locations are defined. below the php block
should be unnecessary as it should inherit from the parent but it
doesn't. i've got some more complex setups too that get hard to
support due to having regexps and "stop processing" instructions in
place, but without them the site doesn't work properly, etc...

server {
        listen 80;
        server_name foo.com;
        index index.php index.html;
        root /home/foo/docroot.com;
        include /etc/nginx/defaults.conf;
       location ~* \.(jpg|jpeg|gif|css|png|js|ico|html)$ {
           expires max;
        location ^~ /blog/wp-admin {
                auth_basic "wordpress";
                auth_basic_user_file /path/to/.htpasswd;
                location ~ \.php$ {
       location ~ \.php$ {

Maybe instead have something like this, which would apply this
location block -after- all others are done...

       location :~ \.php$ {

I picked ":" randomly. Not sure what the best thing is. ^~* are taken,
# is comments, $ is variables, @ is named location, + - & % : ?  are
the only chars left I can think, unless you somehow figured out how to
make it use a keyword like

location :~ \.php$ global {

but I don't know how that will work...

Just an idea. Would simplify configuration a lot. I wind up hitting
the expires stuff a lot when it should be matching another location
instead, but because it's a .js file, it doesn't, so I have to wind up
nesting the expires stuff inside of the location block...

This would help solve some of my issues with locations. That's
probably the most complicated thing in nginx.

More information about the nginx mailing list