Muy buena
El 7 de febrero de 2012 13:53, Filipe Sousa escribió:
> I have implemented a Filter according to this
>
> http://seewah.blogspot.com/2009/02/gwt-tips-2-nocachejs-getting-cached-in.html
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Tool
I have implemented a Filter according to this
http://seewah.blogspot.com/2009/02/gwt-tips-2-nocachejs-getting-cached-in.html
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.co
Thomas, what do you mean by "touch" your no cache.js file? I have
this Chrome caching issue not only when rolling back, but also when
deploying new version. Is there a way to do this via ant or during
the GWT compile? My ant compile looks like this.
Your browser asks for the no cache.is with an If-Modified-Since header, so once
you get a fresher file you cannot get back an older one. You should "touch"
your no cache.js file so it has a later modification date.
--
You received this message because you are subscribed to the Google Groups
"G
I am having issues relating to GWT caching of files. if I roll out a new
version of my application (via a war file deployed to my jetty server). I
am able to bring up chrome and everything looks ok. But if I need to
rollback the version (redeploy an older war file), then I get all sorts of
