2013/5/15 Svoop :
> However, I found a way to pass the correct content type in the routing table.
… which you may want to share, so that later people can look for a
working solution?
Regards, Andre
___
nginx mailing list
nginx@nginx.org
http://mailman.
Richard Stanway 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
On Tue, May 14, 2013 at 5:47 PM, Svoop wrote:
> Hi
>
> I'm setting a custom 404 page with:
>
> server {
> ...
> error_page 404 /errors/not-found.html;
> }
...
>
> Any idea what I'm doing wrong here?
>
> Thanks!
>
Looks like your 404s are being generated by a backend, not by nginx. You
may w
Hi
I'm setting a custom 404 page with:
server {
...
error_page 404 /errors/not-found.html;
}
And the page looks as follows:
Seite nicht gefundenDie angeforderte Seite existiert
nicht.Page non trouvéeCette page n'éxiste pas.Page Not FoundThis page does not exist.
This is what I get with "cu
