Sorry that my first posting here is a support request/bug report, but
I’ve gotta start somewhere!
So - basically, we’re seeing responses occasionally (not always - in
fact, quite infrequently) coming back with a 0 prepended to the entire
response - before the headers.
This means that the response received by the browser ends up looking
HTTP/1.1 200 OK
Date: Tue, 01 Feb 2011 09:07:27 GMT
Content-Type: text/html; charset=utf-8
Set-Cookie: blu-session-id=2baf936adc11f79aad72827d46fd31aa; path=/;
Expires: Mon, 1 Jan 2001 00:00:00 GMT
Last-Modified: Tue, 01 Feb 2011 09:07:27 GMT
Cache-Control: no-store, no-cache, must-revalidate, max-age=0,
p3p: CP=“IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND
and then a load of gzip’d data.
This of course breaks all sorts of behaviour. We initially thought it
was coming from HttpProxyModule, however after reconfiguring to serve
certain assets directly from disk, rather than via the proxy, we saw the
same issue repeating itself, meaning that it’s probably independent from
the proxy module.
Has anyone seen this behaviour before? Any ideas on where it’s coming
Thanks in advance!