Posted by Neredbojias on 04/26/06 02:01

To further the education of mankind, "Alan J. Flavell"
<flavell@physics.gla.ac.uk> vouchsafed:

> On Tue, 25 Apr 2006, Neredbojias wrote:
>
>> I'm only casually familiar with caching mechanisms in general but
>> this statement surprised me because I've been having a bit of
>> trouble with Firefox and caching. 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. Sure, I can manually reload the page
>> and _then_ get the new version, but this shouldn't be necessary.
>> I've checked in Firefox's "tools" menu and didn't see anything that
>> might address the issue.
>>
>> Any thoughts?
>
> It worries me that so many useful settings that are present in the UI
> of Mozilla/Seamonkey, have been ripped out of Ff. Short of finding an
> extension which does what you want, one needs to resort to
> manipulating about:config, if you can work out what the values mean.
>
> If you try about:config, I predict you will find that
> browser.cache.check_doc_frequency is set to 3, which apparently means
> "check when the page is out of date". A value of 1 here would mean
> "Check every time", which might be what you want.
>
> Other values which can be discerned in Seamonkey seem to be 2 meaning
> "never" and 0 meaning "once per session". AFAICT and YMMV.

Ah, that's it (-I think)! I've always used "once per session" in IE and
never had trouble, so I'll try that.

> Alternatively, you can install Pederick's web developer, and use it to
> disable the cache while you are doing web development.

I have it (-and, btw, believe it's one of the best pieces of software ever
made,) but would prefer the configuration approach instead.

As always, thanks for the very helpful and significant reply.


--
Neredbojias
Infinity has its limits.

[Back to original message]