Skip to content
This repository was archived by the owner on Apr 10, 2025. It is now read-only.

Caching headers are not set correctly on some sites #179

Closed
GoogleCodeExporter opened this issue Apr 6, 2015 · 13 comments
Closed

Caching headers are not set correctly on some sites #179

GoogleCodeExporter opened this issue Apr 6, 2015 · 13 comments

Comments

@GoogleCodeExporter
Copy link

On http://law.thu.edu.tw/ we are seeing the wrong caching header, and the 
'repair' header that our module adds early is not removed.

What is the expected output? What do you see instead?

Expected:  Cache-Control:               max-age=31536000
Actual:    Cache-Control:               public, max-age=600
           X-Mod-Pagespeed-Repair   max-age=31536000

What version of the product are you using (please check X-Mod-Pagespeed
header)?

0.9.14.0-349

Please provide any additional information below, especially a URL or an
HTML file that exhibits the problem.

Note the following modules loaded into Apache on this site:

Include "/usr/local/apache/conf/mod_mono.conf"
Include "/usr/local/apache/conf/php.conf"
Include "/usr/local/apache/conf/includes/errordocument.conf"
Include "/usr/local/apache/conf/jk.conf"
Include "/usr/local/apache/conf/mod_bandwidth.conf"
Include "/usr/local/apache/conf/modsec2.conf"


Original issue reported on code.google.com by jmara...@google.com on 5 Jan 2011 at 6:09

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant