Status code 000 in the logs

Maxim Dounin mdounin at
Mon Sep 16 16:46:58 UTC 2013


On Mon, Sep 16, 2013 at 12:22:17PM -0400, monkeybrain wrote:

> What does status code 000 mean in the Nginx logs? I have the following in
> the config:
>         location  =  /
>         {
>             limit_req  zone=slow  burst=10;
>             proxy_pass  http://service_perl;
>         }
> generates an image, writes it to disk and then returns
> "X-Accel-Redirect" to the image. Everything seems to be working just fine, I
> see delayed responses because of limit_req in the logs (with code 200).
> Sometimes there are responses with code 503 for "greedy" clients that exceed
> the burst=10 parameter. All as expected. 
> However, occasionally I see a bunch of requests (around 5 to 20 within a few
> seconds of each other) with status code 000 and 0 for the body size in the
> logs. They are always from the same IP address for the entire bunch, so I'm
> guessing it's requests that already went through internal "X-Accel-Redirect"
> redirect and then something happened. Connection aborted? Something else?
> Why not status code 503? That's where you come in with a helpful
> explanation. :)

It happens if client closes connection whily waiting for limit_req 
delay, and correct code to log is 499 (client closed request).  
This is already fixed in 1.5.3 with the following commit:

Maxim Dounin

More information about the nginx mailing list