Nils Ellmenreich wrote:
>>>> "DF" == Darin Fisher <[EMAIL PROTECTED]> writes:
>>>
>
> >> I suspect a bug in the current disk cache in current builds (although an
> >> URL is cached and the ID is found in the DB, sometimes the file is still
> >> retrieved again over the net). Before I file another bug, I'd like to
> >> investigate further and maybe provide a patch.
>
> DF> Per RFC2616, cached items may expire after some time, requiring the user
> DF> agent (mozilla) to validate the cached items against the origin server.
> DF> Hence, even though mozilla is caching items in its DB, it may still have
> DF> to fetch new copies of those items.
>
> Ok, I'm aware of that but I'm talking about a few seconds of time here.
>
> I've been playing around with going back and forth between two
> pages. Within a few seconds, normal jpegs on a page shouldn't
> expire. However, if I go back to the previous page (which should be
> still in cache), I frequently encounter on pages with many images that
> there are reloads (at least, of some of them, usually a different set
> every time).
>
> I've recompiled all files in mozilla/netwerk/cache/filecache with flag
> DEBUG_dp to see what's going on in the cache. On reload, it find's valid
> cache entries in the cache DB, but still often loads some of them over
> the net (I use the junkbuster proxy to see what's actually loaded).
>
> I suspect a bug here that sometimes prevents a cache hit where there
> should be one. But as I said, it takes time to look into the cache code
> and look for a possible bug (I've tried it already, but I have some
> questions concerning the code before I could proceed) - but if it's
> being rewritten anyway I'd be wasting my time, which I dont want :-)
>
> At least I'd look into it so far to be sure if there's something wron
> and file a bug report. What do you think?
>
> Regards, Nils
Check the Expires tag in about:cache to see if it explains things.
Perhaps the time of day according to the server is not in sync with the
time of day according to your system? Also, what is the behavior of
NS4.x? If you are even just fairly convinced that this could be a bug,
go ahead an open up a bugzilla bug for this... and, post the bug number
on this thread.
Thanks!
Darin
