Welcome! Log In Create A New Profile

Advanced

Re: Client closed connection: 400 vs 499

Maxim Dounin
June 15, 2015 10:26AM
Hello!

On Mon, Jun 15, 2015 at 11:20:15AM +0300, Sorin Manole wrote:

> Hello,
>
> It seems that if the client closes the connection during a requests there
> are time when the request is logged as 400 and other times as 499.
>
> Is there a reason for the difference? Serving of the error page cannot be
> it because the connection is closed anyway.

The "400" code means that no correct request was received - that
is, client sent a bad request.

The "499" code means that nginx got a request, but wasn't able to
send a response. That is, client closed connection before we
started sending a response. This, in particular, may happen if a
backend is slow and nginx isn't able to return a response before
the client times out.

The difference may be important when looking into logs.

--
Maxim Dounin
http://nginx.org/

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
Subject Author Views Posted

Client closed connection: 400 vs 499

Sorin Manole 657 June 15, 2015 04:30AM

Re: Client closed connection: 400 vs 499

Maxim Dounin 646 June 15, 2015 10:26AM



Sorry, you do not have permission to post/reply in this forum.

Online Users

Guests: 216
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready