Re: Uncacheable .cache.js files ?

Pro Tip: don't use "refresh" to test caching in Chrome, particularly when Development Tools are open.

When I refreshed Google Groups, the request for the cache.js had a "Cache-Control: max-age=0" header. When copy/pasting the URL to another tab (with Dev Tools open), the file is served from cache.

On Monday, November 3, 2014 12:26:10 PM UTC+1, Frank Taffelt wrote:

Hi,

While analyzing a cache problem, of my own app, i came across a strange issue that i cannot explain. Good thing is, that we have showcase to reproduce the issue (so i think) - google groups itself.

lets take a look into google groups, which is using GWT AFAIK, and see what it request and what it caches. Looking for the first <md5>.cache.js file ( in my case https://groups.google.com/forum/1CC2C4879D0404FA63089F39885AF88D.cache.js at the time of writing for Chrome) shows valid caching headers of one year the response. pressing reload shows that the browser always does a fresh request for <MD5>.cache.js where it could and should use the cached variant from the previous request.

Strange thing is that caching works with the deferred js-variants: https://groups.google.com/forum/deferredjs/1CC2C4879D0404FA63089F39885AF88D/13.cache.js in my test.

Can anybody explain this?

Thanks,

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.