Matthew Wilson wrote:
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?
It seems like this works, at the top of an update RDF served via PHP:
<?php
header('Content-type: text/xml');
$expire = "Expires: " . gmdate("D, d M Y H:i:s", time() + 3600) . " GMT";
header($expire);
?><?xml version="1.0"?>
for the browser to refetch the file after 1 hour. However PHP appears
not to be parsed inside of files named ".rdf", so I had to use
".rdf.php" instead. However all my existing update files are named
".rdf". Is there a mozdev configuration option to allow parsing of PHP
inside .rdf files?
Matthew
_______________________________________________
Project_owners mailing list
[email protected]
http://mozdev.org/mailman/listinfo/project_owners
