Re: Browser Cache issue while switching to new version of GWT Application

On Tuesday, October 21, 2014 10:22:52 AM UTC+2, Jens wrote:

Is there a way to force the browser to recognize the new version?

Yeah tell your server to set correct caching HTTP headers for any file that is of the form *.nocache.*

In your case your <modulename>.nocache.js file is probably cached by the browser but as the file name suggests it should never be cached.

See http://www.gwtproject.org/doc/latest/DevGuideCompilingAndDebugging.html#perfect_caching 

--
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.