According to the doc:
http://wiki.nginx.org/HttpFastcgiModule#fastcgi_intercept_errors

Note: You need to explicitly define the error_page handler for this for it
to be useful. As Igor says, "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."

Actually I still can't understand the exact meaning, so I have done some
experimentd.

1. turn on fastcgi_intercept_errors,
- in the backend php/fcgi send 404 header,
- set the error_page (php)

Result: nginx use the default error template

2. turn off fastcgi_intercept_errors,
- in the backend php/fcgi send 404 header
- set the error_page (php)

Result: now the custom error_page (php) is being used.

So it seems to me that* fastcgi_intercept_errors should be off and set
the error_page *if I need to specify custom error handler, is
this interoperation correct?


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