I suppose it has to do with the fact that error_page masks errors coming
from the backend, impersonating them with nginx.
If nginx shows a 404 when the backend actually generated it, and you digged
improperly into the logs, you might be fooled by that and get lost when
trying to trace the error.

If you decide to use per-backend error pages (to help differentiating where
the error comes from), then the whole thing becomes useless...

Thus, you need to know what you are doing: masking errors from the backend
is IMHO a double-edged sword.
---
*B. R.*

On Mon, Nov 10, 2014 at 1:29 PM, Maxim Dounin <mdounin@mdounin.ru> wrote:

> Hello!
>
> On Fri, Nov 07, 2014 at 02:05:38PM -0500, zappa wrote:
>
> > Btw, why is it you don't recomment using the error_page method?
>
> It's an error-prone approach.
>
> --
> Maxim Dounin
> http://nginx.org/
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx