275078 - Page not always reloaded although it changed (sometimes the chached version is used)

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Andreas Allacher]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5) Gecko/20041108 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5) Gecko/20041108 Firefox/1.0

There is some problem with checking, if the page is newer then the one in the
cache. Sometimes on some pages (can't say which exactly), the cached file is
used, although the page got changed (need to press F5, using the
check_doc_frequency option to set the browser to always reload the page, is of
course not what I want).

Reproducible: Didn't try



Expected Results:  
The behaviour when the cache gets reloaded should get a little overworked
because if the page got changed and I use the old version in the cache, this is
not the expected result..

Comment 1

[Phil Ringnalda (:philor)]

If you can tell us a particular page, then there's something to fix. Otherwise,
we have no way of knowing if you are seeing a page with bad caching headers, or
with perfectly good caching headers that happened to change before the headers
expected it would, or an actual bug.

Comment 2

[Andreas Allacher]

I know that this page didn't get reloaded one time, I go to the URL and instead
of the DH Mod tool V2.1, I still so the DH Mod Tool v2.0b and the screenshot
also was another. I pressed F5 and the right page was loaded...

URL: http://www.driverheaven.net/patje/

Comment 3

[Jaime Mitchell (use [e-mail] for email)]

Reporter are you still able to reproduce this on a given site? Can you provide
the headers sent for that site so that we can see if the cache instructions are
correct.

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.