Apologies - having looked closer I see the bug is with my python test client - python's httplib doesn't notice nginx has closed the connection - it's up to the application code to retry in this case.<br><br>Cheers,<br>
Mike <br><br><div class="gmail_quote">On 20 January 2011 17:45, Mike Bell <span dir="ltr"><<a href="mailto:mdb036@gmail.com">mdb036@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi,<br><br>I'm seeing dropped requests on nginx reload. I'm using 0.8.53 compiled from source.<br><br>My configuration is nginx as a proxy in front of (currently) 2 apache servers.<br><br>It looks like if a client reuses a connection it had before the reload (HTTP/1.1 style), then the server doesn't handle the request - from tcpdump, I see the TCP connection is just reset with no response. <br>
<br>Is this a known issue? Is there some configuration option to stop the old worker processes from dieing until the connections have all timed out?<br><br>Cheers,<br><font color="#888888">Mike<br>
</font></blockquote></div><br>