Can try_files be allowed outside of location {} ?

mike mike503 at gmail.com
Fri Mar 20 08:43:43 MSK 2009


2009/3/19 Igor Sysoev <is at rambler-co.ru>:
> On Thu, Mar 19, 2009 at 10:17:45PM -0700, mike wrote:
>
>> I get a warning when placing it outside of a location block. I don't
>> think it -needs- to be inside of one. Would be nice to team up with
>> the patch you made for the next release... :)
>
> I'm not sure that it should be done.
> Could you show use case ?

for a site basically dedicated to a single app... no need for location / {}

server {
        listen 80;
        server_name michaelshadle.com;
        index index.php index.html;
        root /home/mike/web/michaelshadle.com;
        include /etc/nginx/defaults.conf;
        include /etc/nginx/expires.conf;
        try_files $uri $uri/ /wordpress/index.php?q=$uri;
        location ~ \.php$ {
                fastcgi_pass 127.0.0.1:11000;
        }
}

my current workaround:

server {
        listen 80;
        server_name michaelshadle.com;
        index index.php index.html;
        root /home/mike/web/michaelshadle.com;
        include /etc/nginx/defaults.conf;
        include /etc/nginx/expires.conf;

        location / {
                try_files $uri $uri/ /wordpress/index.php?q=$uri;

        location ~ \.php$ {
                fastcgi_pass 127.0.0.1:11000;
        }
        }
}

A nit bit-picky but I don't see the need for the restriction, unless
the code is very difficult for it.





More information about the nginx mailing list