On Dec 13, 6:19 am, Thomas Broyer <[email protected]> wrote: > On 12 déc, 20:35, omsrobert <[email protected]> wrote: > > > We're using Tomcat 6.0.18 and GWT 1.5.3. The browser (Firefox 3 at > > least) is caching our GWT application. Refreshing fixes it but that's > > not an option for production. I would think this is a common issue. > > How do we fix it? Write a response header filter for Tomcat or is > > there a better way? > > > Here's the HTTP headers: > > >http://ourserver/mywebapp/home/com.mycompany.mine.OurGWTApp.nocache.js > > You should configure your server to send very short expiration for > *.nocache.* (something like 2 minutes) and very long expiration for > *.cache.* (RFC2616 recommends 1 year to indicate a resource is > "permanently cacheable") > > BTW, it all depends how your server is computing the ETag. I'd > recommend disabling ETags altogether.
Does anyone have a sample config snippet for Tomcat? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
