Pagespeed optimized resource sending incorrect Content-Length header

[GoogleCodeExporter]

We think have isolated a problem with Pagespeed on nginx 1.7.30.4 where we 
intermittently get responses for Pagespeed optimised resource URLs that have a 
Content-Length header set where more data is sent than the content-length.

The Pagespeed optimised resource intermittently responds with a 
"Content-Length: 62800", which is the size of the resource on the origin 
servers. Nginx actually transmits 74620 bytes.

While this will be causing protocol violations, when you couple this with 
Varnish, the protocol violation is fixed, because Varnish truncates the content 
to match the content-length header sent by nginx.

This results in broken CSS. When cached by a CDN the problem is further 
exacerbated.

The CSS resources are minified (.cf. in the url). Which also raises the 
question about why the resources are larger than the origin resources.

I can provide URLs out of band and reproduction steps if necessary.

Any help would be appreciated.

Original issue reported on code.google.com by jmara...@google.com on 9 May 2014 at 6:27