jstangroome commented on issue #1556: Combined css returns truncated, 
mis-encoded body on cache hit
URL: 
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-387890251
 
 
   @oschaaf Adding `pagespeed HttpCacheCompressionLevel 0;` does resolve the 
issue.
   
   The requests, once the resource is cached, now return `Transfer-Encoding: 
chunked` and do not include a `Content-Length` response header at all. Most 
importantly the response body is gzipped in concordance with the 
`Content-Encoding: gzip` response header.
   
   The cached object on disk at 
`/var/ngx_pagespeed_cache/v3/eample.com/http,3A/,2Fwww.example.com/css/store.css+vendor.css.pagespeed.cc.HBFc8IpUqh.css,`
 now contains the non-compressed form of the file, and the headers in the cache 
file's preamble no longer contain the invalid `Content-Length` header.
   
   While this workaround solves the immediate issue, I'm wary of the impact it 
will have on an already large volume of cache space used.
   
   Also, it is rather unintuitive that a cached object, stored in gzipped form, 
would be served ungzipped, but the cached object when stored in uncompressed 
form is correctly served gzipped. :S
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to