Possible HTTP response read bug in Nginx 1.0.12

tikonen nginx-forum at nginx.us
Sat May 19 02:29:20 UTC 2012

Running now on nginx 1.2.0 and haven't seen this error anymore in normal

Now I can see these errors only when non-gracefully restarting upstream
nodes, but of course in this case these "prematurely closed"  errors are
expected and normal.

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,224853,226651#msg-226651

More information about the nginx mailing list