How to allow 404 server error to propagate to the user

Thu Nov 28 12:57:37 UTC 2013

I am currently raising a 404 error from the backend server (running on port
9000), but nginx, instead of giving the client the same 404 error, responds
with a 505, but still send the body of the response that is returned from
the server with the 404.

How do I fix this?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20131128/46871825/attachment.html>