Hi, Has anybody every encountered this with far futures caching?
For some reason “unset” and “set” don’t work. “Unset” doesn’t remove the header value. And “set”, which is supposed to remove the current value and use the new, only adds the new value onto the old resulting in two values for a given header item! My host is baffled and I may go nuts.
My goal, for JS is to:
remove last modified
set expires modified header - access plus 1 year
set cache control header - access plus 1 year
Header unset Pragma
Header unset ETag
Header unset Expires
Header unset Cache-Control
Header set Cache-Control “max-age=31536000,public”
Header set Expires “A31536000”
Header unset Last-Modified
I realize I shouldn’t have to use unset Expires and unset Cache-Control. But even explicitly doing it, it doesn’t remove the old values! YSlow shows that my new values are only being appending ONTO the old. So there’s TWO values for each. Any ideas what’s wrong? Is it possible that a host’s server can force these values to remain?
Response header as shown in Yslow:
Date Fri, 28 Jan 2011 00:26:05 GMT
Last-Modified Thu, 27 Jan 2011 23:21:28 GMT
Cache-Control max-age=63556926,public, max-age=0
Expires A63556926, Fri, 28 Jan 2011 00:26:05 GMT