Welcome! Log In Create A New Profile

Advanced

Re: HTTP 400 responses

Muhui Jiang
October 21, 2015 04:00AM
>>client prematurely closed connection
that means your client has closed the socket.

You can rebuilt the nginx to enable the detailed logging for debug
http://nginx.org/en/docs/debugging_log.html

2015-10-21 15:52 GMT+08:00 Pauls V <nginx-forum@nginx.us>:

> Had tried with reload and that didn't change output. Tried restarting Nginx
> and that actually enabled the logging.
>
> If someone is wondering then this is what I see in log now:
> ... client prematurely closed connection ...
>
> Thanks,
> Pauls
>
> Posted at Nginx Forum:
> https://forum.nginx.org/read.php?2,262308,262385#msg-262385
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

HTTP 400 responses

Pauls V October 19, 2015 07:23AM

Re: HTTP 400 responses

Maxim Dounin October 19, 2015 10:06AM

Re: HTTP 400 responses

Pauls V October 21, 2015 03:52AM

Re: HTTP 400 responses

Muhui Jiang October 21, 2015 04:00AM

Re: HTTP 400 responses

Pauls V October 21, 2015 04:22AM

Re: HTTP 400 responses

Pauls V October 21, 2015 05:46AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 86
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready