A: 

I am also facing this issue? Do you know yet what was causing issue in your case

splendid
A: 

We were having a similar situation running Apache 2.0.59 with WebLogic 10mp2. Intermittently, we would find data sitting in front of a valid HTTP response. The data was always a gzipped 0 after a 304 Not-Modified response. The corrupt header begins with the signature 1F 8B 08...

The issue seemed to stem from the use of mod_deflate with cached resources. We have been able to eliminate the issue by disabling mod_deflate. To date, we have disabled mod_deflate wholesale, but are working on narrowing down where we disable mod_deflate. The Apache WebServer project alludes to a fix in 2.1.1:

*) mod_deflate: Don't deflate responses with zero length e.g. proxied 304's [Allan Edwards]

Joey