How to allow 404 server error to propagate to the user

[Debasish Ray Chawdhuri]

The log created are as follows

14.141.60.139 - - [28/Nov/2013:13:24:13 +0000] "GET /afasdfadsfsadf
HTTP/1.1" 505 5 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:25.0)
Gecko/20100101 Firefox/25.0"
14.141.60.139 - - [28/Nov/2013:13:24:19 +0000] "-" 400 0 "-" "-"



On Thu, Nov 28, 2013 at 6:27 PM, Debasish Ray Chawdhuri <
debasish at geekyarticles.com> wrote:

> 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/0c7cf0bd/attachment.html>