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

Pete Collins pete at mozdevgroup.com
Mon Jul 24 12:10:48 EDT 2006



Matthew Wilson wrote:

> Brian King wrote:
>
>> Alex Eng wrote:
>>
>>>> I believe the best solution is for the web server to serve up the 
>>>> (RDF) files with the no-cachhe directive:
>>>>
>>>> header("Cache-Control: no-store, no-cache, must-revalidate");
>>>>
>>>> Do you know what server is being hit for your updates?
>>>>
>>>> Related reading:
>>>> http://www.websiteoptimization.com/speed/tweak/cache/
>>>>
>>>
>>> The update manifest for my extension, Clippings, resides on the 
>>> Mozdev site for my project.
>>
>>
>> http://clippings.mozdev.org/update.rdf  ??
>>
>> Pete, how's the MDG (www) server set up to handle RDF files with 
>> regard to caching?
>
>
> LiveHTTPheaders shows no explicit caching directives.
>
> about:cache seems to show an expiry time of about 5 and a half hours.
>
>
Not sure about Mozdev, I'll have to check. BUt I usually set rdf fiels to:

  header("Cache-Control: no-store, no-cache, must-revalidate");

to avoid browser caching ...

--pete

-- 
Pete Collins - Founder, Mozdev Group Inc.
www.mozdevgroup.com
Mozilla Software Development Solutions
tel: 1-719-302-5811
fax: 1-719-302-5813



More information about the Project_owners mailing list