Perhaps your web server is setting an "Expires" header on the response for js files for some time in the future?
From: Colin Bleckner [mailto:[email protected]] Sent: Friday, November 13, 2009 2:21 PM To: Aaron Boodman Cc: [email protected] Subject: Re: [chromium-extensions] Chrome caching Javascript files Thanks for the tip, that does the trick for now. I filed this as well: http://code.google.com/p/chromium/issues/detail?id=27661 Colin Aaron Boodman wrote: On Fri, Nov 13, 2009 at 1:29 PM, Colin Bleckner <mailto:[email protected]> <[email protected]> wrote: I have a very simple content script that current grabs a remote Javascript file and inserts it into the current page*. Unfortunately, Chrome seems to aggressively cache that file. For testing, my remote file is as simple as "alert('loaded');". If I close Chrome and change the alert to something else (like "alert('new loaded');"), and then start Chrome again, it continues to show the old alert message. The only way I can get Chrome to load the new file is to clear my cache through the settings. Is there a way I can get Chrome to not cache that file as aggressively as it is right now? That sounds like a bug, but the classic work around is to append a unique token to the URL, like: req.open("GET", <http://someserver.com/blah/foo.js?r=> "http://someserver.com/blah/foo.js?r="; + new Date().getTime(), false); - a -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" 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/chromium-extensions?hl=. -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" 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/chromium-extensions?hl=.
