3 ms·
Maybe it's just that they don't want that one page cached as they may update their scripts, images and stylesheets. And for that css-file, I think that whenever
by eonwe 15y ago
Maybe it's just that they don't want that one page cached as they may update their scripts, images and stylesheets.
And for that css-file, I think that whenever they change the css, they'll just give the resource a new address so cache is only invalidated when there are actual changes.
- newman314 15y agoThat does not make sense. If they update that page, then it'll get refreshed when it expires. For the CSS file, some browsers are buggy so it really should be set to "Cache-Control: public". See http://www.acunote.com/blog/2008/07/why-you-should-use-cache-control-pupblic-for-caching-to-work-with-ssl.html http://www.acunote.com/blog/2008/07/why-you-should-use-cache...