client disconnects

[Frank Liu]

Hi,

Thanks for the clarification!
What would we see if the client disconnects in the middle of nginx sending
the response? Will there be a "while .." clause in the error log? Will the
http status code be reset to 499?

Thanks!
Frank


On Wed, Nov 25, 2020 at 5:34 AM Maxim Dounin <mdounin at mdounin.ru> wrote:

> Hello!
>
> On Tue, Nov 24, 2020 at 08:23:08PM -0800, Frank Liu wrote:
>
> > When a client disconnects (initiated tcp FIN), shouldn't we see 499 in
> > nginx logs? But sometimes I see 400, along with below in error log:
> > *2314539 client prematurely closed connection, client: x.x.x.x,
> >
> > Since I don't see "while reading client request headers" in the error
> log,
> > I assume the request is already received (or maybe "body" hasn't arrived
> > fully yet?) when client disconnects.
> >
> > When would nginx log 400 instead of 499? The error log ("info" level) is
> > not clear about why 400, other than "client prematurely closed
> connection,
> > ".
>
> The 400 error along with "client prematurely closed connection"
> and without an "while ..." clause implies that the connection was
> closed while reading the request body.
>
> --
> Maxim Dounin
> http://mdounin.ru/
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20201125/e7522188/attachment.htm>