Comment #4 on issue 25262 by mark11born: excessive caching of extension source http://code.google.com/p/chromium/issues/detail?id=25262
Seeing this as well. When we deploy to our (internal) test server I run a script which releases an extension and updates the update manifest XML. Updating the installed extension from within Chrome fails unless the cache is emptied first. Witnessed with 4.0.249.11 on Windows XP and 4.0.249.12 on Snow Leopard. I'm also suspecting that the manifest XML file is being cached. The web server does not return any caching headers, save for a Last-Modified which as far as I can tell is correct, except that it's several hours *ahead* of time… So, however, is the Date header, so I guess that should counteract the incorrect date. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
