search

crowell / modpagespeed_tmp

Automatically exported from code.google.com/p/modpagespeed
Apache License 2.0
0 stars 0 forks source link

do not reduce the strength of cache-control restrictions on HTML #730

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently, by default mod_pagespeed will erase whatever cache-control headers 
are supplied from origin, and replace with max-age=0, no-cache.  That might 
actually increase the cacheability of the HTML, which might have "nostore".

I think the default we picked is OK as a minimally severe caching restriction, 
but we should not strip a 'nostore' if it's present.

Original issue reported on code.google.com by jmara...@google.com on 25 Jun 2013 at 2:42

GoogleCodeExporter commented 9 years ago

Original comment by jmara...@google.com on 25 Jun 2013 at 1:24

GoogleCodeExporter commented 9 years ago 
In addition to "no-store", we should retain must-revalidate, post-check=0, 
pre-check=0.

More generally, we should simply retain all CC fields we don't specifically 
want to change.

Original comment by jmara...@google.com on 25 Jun 2013 at 1:31

GoogleCodeExporter commented 9 years ago

Original comment by jmara...@google.com on 25 Jun 2013 at 1:59