error_page without content type

Svoop svoop at
Wed May 15 11:20:26 UTC 2013

Richard Stanway <r1ch+nginx at ...> writes:
> Looks like your 404s are being generated by a backend, not by nginx. You
may want to use fastcgi_intercept_errors / proxy_intercept_errors.

You're right, but since the pages are served via Passenger, these directives
won't work. However, I found a way to pass the correct content type in the
routing table.


More information about the nginx mailing list