[Bug 12904] Force browser to load new javascript files after upgrade
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12904 --- Comment #56 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- (In reply to Kyle M Hall from comment #54)
I'm at a loss. I just rebased and squashed/split all these patches for readability. Everything is working, but the browser continues to indicate it's grabbing cached files even when the filename has changed!
At first I thought it was because the rewrite was doing a 301 redirect, so I removed that, and still had the same thing. Next I tried a 307, but again, the same results ( though chrome decided not to cache some files at all with a 307 ).
Here is a video demonstration: http://screencast.com/t/JfFonhkWax
Martin, Jonathan, any ideas on what is going on?
Kyle
Using firebug (network tab) that sounds ok for me: (reload mainpage) mainpage_16.0600014.css 301 (moved permanentely) mainpage.css 200 (click on mainpage) nothing # from cached (change version using the interface, so the page reload and will hit some .css and .js files, that's why we are focusing on mainpage.css) (click on mainpage) mainpage_16.0600014.css 301 (moved permanentely) mainpage.css 200 -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org