Shouldn't this trigger an nginx 404?
Igor Sysoev
is at rambler-co.ru
Thu Mar 26 12:17:38 MSK 2009
On Thu, Mar 26, 2009 at 01:13:31AM -0700, Michael Shadle wrote:
> 2009/3/26 Igor Sysoev <is at rambler-co.ru>:
>
> > Besides "fastcgi_intercept_errors on" you also need
> >
> > error_page 404 /404.html;
> >
> > nginx does not intercept an error if there is no custom handler for it:
> > it does not show its default pages. This allows to intercept some errors,
> > while passing others as are.
>
> This would be good to document. I will try to remember to add it to the wiki.
>
> > location ~ ^/files/(.*) {
> > fastcgi_pass 127.0.0.1:11021;
> > fastcgi_param SCRIPT_FILENAME /path/to/foo.php;
> > fastcgi_param QUERY_STRING file=$1;
> > }
>
> Is there any performance benefit here? Rewrite seems simple.
Yes, this is slighty faster.
> Any I
> would like to use try_files for any possible situation that it is
> suitable for now ;)
--
Igor Sysoev
http://sysoev.ru/en/
More information about the nginx
mailing list