I have recently discovered that, after version deployments, our GWT application does not work in some users' browsers unless they do a hard refresh on the browser.
A bit of investigation revealed that this is because their browsers are caching the all-important YOUR_MODULE_NAME.nocache.js file. I also found this thread http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/708cbcca4d3bd4eb, amongst others, discussing this topic. I have sinced posted a blog which includes the implementation of a filter to stop browsers and proxies from caching the file: http://seewah.blogspot.com/2009/02/gwt-tips-2-nocachejs-getting-cached-in.html Hope you will find it useful. See Wah --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
