|
|
Posted by Neredbojias on 04/26/06 02:08
To further the education of mankind, Michael Winter
<m.winter@blueyonder.co.uk> vouchsafed:
> On 25/04/2006 19:41, Neredbojias wrote:
>
>> To further the education of mankind, Michael Winter
>> <m.winter@blueyonder.co.uk> vouchsafed:
>>
>>> Fx takes a different approach, and always revalidates whenever the
>>> lifetime is unknown (though there an advanced property,
>>> browser.cache.check_doc_frequency, that will that).
>
> That statement isn't meant to be as absolute as it appears, above.
>
> [snip]
>
>> Whenever I change/update a page on my site and then open it with FF,
>> I always seem to get the old version. None of my pages have any
>> explicitly-stated caching directives, meta or otherwise.
>
> [snip]
>
>> Any thoughts?
>
> Not particularly, but I've never had that problem, and it's difficult to
> diagnose remotely. So, we'll start with the obvious (I'll apologise now
> for asking anything too obvious), and go from there. :-)
>
> What doesn't get updated? Document content? The style sheet?
>
> Have you checked your server logs to determine if a request was sent?
> What about the response headers to ensure that validators (both ETag and
> Last-Modified) have changed from their previous values after the update?
Well, I must admit that I hadn't done any of that, but it will be the next
step if the "about:config" setting doesn't work. Actually, I'm not all
that familiar with even _how_ to check such headers, but <sigh> I s'pose
I'll have to learn one of these days. It was the content, btw: the content
(ie: page itself) wasn't replaced with the newer version. I do expect that
the browser_cache...."once per session" setting will work, though.
Mucho thanks for the information and assistance.
--
Neredbojias
Infinity has its limits.
Navigation:
[Reply to this message]
|