Firefox is caching GWT.nocache.js even with no-cache headers

Asked Sep 12 '13 at 17:34

Active Sep 13 '13 at 09:54

Viewed 287 times

I'm having troubles with firefox caching using GWT, if I deploy site second time, FF on page load will use cached .nocache.js, which can't load page logics, so I will see blank screen. I tried to set headers as it was described here, but FF is still caching, but not on hard drive, but in memory. Changing

<script type="text/javascript" language="javascript" src="ModuleName/ModuleName.nocache.js"></script>

<script type="text/javascript" language="javascript" src="ModuleName/ModuleName.nocache.js?v=90?"></script>

will help, but it's not comfortable to change parameter each time I'm deploying. Using Tomcat7, GWT 2.5.1, FF 23.0.1.

What i got after second deploy with header filter: http://imageshack.us/photo/my-images/827/vwn0.jpg/ . As you can see, headers are setted but FF is still caching .nocache.js in memory and using it.

How can it be resolved?

edited Sep 13 '13 at 09:54

asked Sep 12 '13 at 17:34

Naturlih

Strange, I use almost exact same code and it works for me. Are you sure that your filter gets invoked? – David Levesque Sep 12 '13 at 21:59
Strange... Solutions can be found at http://stackoverflow.com/questions/118884/what-is-an-elegant-way-to-force-browsers-to-reload-cached-css-js-files – Olivier Tonglet Sep 13 '13 at 06:57
@Naturlih: did you check the headers are correctly sent? (in Firefox developer tools) – Thomas Broyer Sep 13 '13 at 07:50
@ThomasBroyer: I've updated post, as you can see headers are setted correctly, FF is using expired cache. – Naturlih Sep 13 '13 at 09:49

Firefox is caching GWT.nocache.js even with no-cache headers

0 Answers0