<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: Arial; ">You're absolutely correct - I've just applied the patch, rebuilt, run through a few million requests, and it's no longer happening.</span></span></div><div><br class="webkit-block-placeholder"></div><div>Thanks so much!</div><div><br></div><div>Maxwell</div>
<br><div><div>On 1 Feb 2011, at 10:50, Maxim Dounin wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hello!<br><br>On Tue, Feb 01, 2011 at 10:14:19AM +0000, Maxwell Lamb wrote:<br><br><blockquote type="cite">Hi All,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Sorry that my first posting here is a support request/bug <br></blockquote><blockquote type="cite">report, but I've gotta start somewhere!<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">So - basically, we're seeing responses occasionally (not always <br></blockquote><blockquote type="cite">- in fact, quite infrequently) coming back with a 0 prepended to <br></blockquote><blockquote type="cite">the entire response - before the headers.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">This means that the response received by the browser ends up <br></blockquote><blockquote type="cite">looking like<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">************<br></blockquote><blockquote type="cite">0<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">HTTP/1.1 200 OK<br></blockquote><blockquote type="cite">Server: nginx/0.8.53<br></blockquote><blockquote type="cite">Date: Tue, 01 Feb 2011 09:07:27 GMT<br></blockquote><blockquote type="cite">Content-Type: text/html; charset=utf-8<br></blockquote><blockquote type="cite">Transfer-Encoding: chunked<br></blockquote><blockquote type="cite">Connection: keep-alive<br></blockquote><blockquote type="cite">Set-Cookie: blu-session-id=2baf936adc11f79aad72827d46fd31aa; path=/; HttpOnly<br></blockquote><blockquote type="cite">Expires: Mon, 1 Jan 2001 00:00:00 GMT<br></blockquote><blockquote type="cite">Last-Modified: Tue, 01 Feb 2011 09:07:27 GMT<br></blockquote><blockquote type="cite">Cache-Control: no-store, no-cache, must-revalidate, max-age=0, post-check=0, pre-check=0<br></blockquote><blockquote type="cite">Pragma: no-cache<br></blockquote><blockquote type="cite">p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"<br></blockquote><blockquote type="cite">Content-Encoding: gzip<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">and then a load of gzip'd data.<br></blockquote><blockquote type="cite">*************<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">This of course breaks all sorts of behaviour. We initially <br></blockquote><blockquote type="cite">thought it was coming from HttpProxyModule, however after <br></blockquote><blockquote type="cite">reconfiguring to serve certain assets directly from disk, rather <br></blockquote><blockquote type="cite">than via the proxy, we saw the same issue repeating itself, <br></blockquote><blockquote type="cite">meaning that it's probably independent from the proxy module.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Has anyone seen this behaviour before? Any ideas on where it's <br></blockquote><blockquote type="cite">coming from?<br></blockquote><br>This looks like duplicate last chunk ("0" CRLF CRLF) in previous <br>request. There is at least one known problem with proxy_cache <br>(with proxy_cache_use_stale) which results in such behaviour.<br><br>If you use proxy_cache you may test if switching it off (or at <br>least disabling proxy_cache_use_stale completely) resolves the <br>problem. Alternatively, apply patch from here:<br><br><a href="http://nginx.org/pipermail/nginx-devel/2010-January/000102.html">http://nginx.org/pipermail/nginx-devel/2010-January/000102.html</a><br><br>Maxim Dounin<br><br>_______________________________________________<br>nginx mailing list<br>nginx@nginx.org<br>http://nginx.org/mailman/listinfo/nginx<br></div></blockquote></div><br></body></html>