On Sun, Jan 4, 2015 at 7:27 PM, James Nelson <ja...@wetheinter.net> wrote:
> You are expected to tell your web server to set non-caching headers for > that file, so if your browser is caching it at all, I would say you need to > modify your webserver cache policy. > On Sun, Jan 4, 2015 at 7:28 PM, James Nelson <ja...@wetheinter.net> wrote: > Oh, wait, sorry, I see you're dealing w/ offline support. > > I will politely bow out and wish you luck in diagnosing the problem. > Nope you are right. You still need to set the cache control headers, even when dealing with offline support. We use gwt-appcache [1] but still use gwt-cache-filter [2] to set the headers. My guess is that it it is the fact that the gwt compiler is not updating the timestamp and something in the chain (tomcat?) is not noticing the file is changed and serving the cached version. [1] https://github.com/realityforge/gwt-appcache [2] https://github.com/realityforge/gwt-cache-filter -- Cheers, Peter Donald -- 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+unsubscr...@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.
