[Project_owners] Unwanted update manifest (update.rdf) caching

Matthew Wilson matthew at mjwilson.demon.co.uk
Sat Jul 22 17:33:08 EDT 2006


Matthew Wilson wrote:
> Alex Eng wrote:
>> During testing of a new version 2.0 release of my Firefox extension, 
>> Clippings, I noticed that Firefox won't update the extension from a 
>> previous release either automatically, or manually in the Extensions 
>> window, unless I clear the browser cache first.
> 
> I get this too. My experience is as follows: When I get this scenario, 
> if I load the update RDF directly in the browser, then I get the old 
> version. If I shift-reload then I get the new version, and the Extension 
> Manager does the update.
> 
> Strangely enough it appears that the Extension Manager does attempt to 
> overcome caching problems: 
> http://lxr.mozilla.org/mozilla1.8/source/toolkit/mozapps/extensions/src/nsExtensionManager.js.in#6163 

https://bugzilla.mozilla.org/show_bug.cgi?id=298305 says
"We follow the normal network-cache rules here, where the server that 
provides
the update RDF can decide how long it is allowed to persist in the cache. I
don't think this is something we want to fix."

Has anyone successfully set expiry times or maxage headers on their 
update.rdfs?

Matthew





More information about the Project_owners mailing list