> Hello,
>
> Everyone knows there are many nginx tutorials out there and I would like
> to
> know what's the "modern way" when writing a php location block, I'm doing
> (nginx 1.1.:
>
> location ~ \.php$ {
> try_files $uri =404;
>
> include fastcgi_params;
> fastcgi_pass unix:/var/run/php5-fpm/www-data.sock;
> }

This is a "generic" way. This way you don't enumerate all the PHP scripts
that are to be executed. The above is just the Nginx translation of
"default" Apache way.

There are better ways IMHO. But they require more effort to put in place.

Also there's no need to use fcgi_split_pathinfo even if your app uses
PATHINFO, like Chive for example. You can get the same employing named
captures with regex based locations.

--appa

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx