New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

when the server provides an Expires header, our cache extension may not work everywhere #34

Closed
GoogleCodeExporter opened this Issue Apr 6, 2015 · 3 comments

Comments

Projects
None yet
1 participant
@GoogleCodeExporter

GoogleCodeExporter commented Apr 6, 2015

In some configurations, Apache will add an Expires header to resources.

This can conflict with our cache extension headers, which use Cache-Control: 
max-age.

In most cases this is a non-issue since CC max-age is preferred to Expires per 
the HTTP/1.1 RFC.

However Firefox (through v4?) and HTTP/1.0 proxies will use Expires when both 
are present.

When an Expires header is present, we should overwrite it with a date that 
matches the value in the CC max-age header.

Original issue reported on code.google.com by bmcqu...@google.com on 6 Nov 2010 at 11:57

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

Should we remove 

Original comment by jmara...@google.com on 18 Nov 2010 at 2:37

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

Fixed in http://code.google.com/p/modpagespeed/source/detail?r=231

Original comment by jmara...@google.com on 18 Nov 2010 at 10:52

  • Changed state: Fixed
@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

Original comment by sligocki@google.com on 23 Nov 2010 at 11:43

  • Changed title: when the server provides an Expires header, our cache extension may not work everywhere
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment