292693 - Etag header or caching ignored on pages after firefox opened for a long period of time

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Michael Blake]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

It seems that after leaving FF open for long periods of time (weeks) there comes
a point when things aren't being cached properly preventing Etags from working
(a HTTP Request/Response Header). 

Memory usage/ Virtual Memory usage is usually quite high, 200 MB+, (even with
one page open for weeks) and it seems that the cacheing might be being ignored
OR FF is not sending out the Etag headers and always requesting a clean copy of
the image.

Reproducible: Didn't try

Steps to Reproduce:
1. Left browser open for weeks. Normal everyday use.
2. Watched HTTP headers and realised that Etags were being ignored at some point
3. Restarted browser and all was OK.



Expected Results:  
The images should have been cached and an Etag + IfNoneMatched header sent and
compared with the server.

Comment 1

[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 2

[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.