There is a bug in GWT 2.7 for the no cache file having the wrong timestamp and being cached when it shouldn't as a result.
We haven't seen this bug when using GWT 2.8-beta1. On Tue, Jul 5, 2016 at 11:58 AM, Jens <[email protected]> wrote: > Most likely a caching problem in your browser (your > <modulename>.nocache.js file is probably cached by the browser and asks for > an old permutation). *.cache.* and *.nocache.* must have correct HTTP > caching headers. > > > http://www.gwtproject.org/doc/latest/DevGuideCompilingAndDebugging.html#perfect_caching > > -- J. > > -- > You received this message because you are subscribed to the Google Groups > "GWT Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
