does not see changes to html, requiring manual cache flush




Networking: Cache
15 years ago
13 years ago


(Reporter: Warren Keuffel, Assigned: gordon)



Mac OS X

Firefox Tracking Flags

(Not tracked)





15 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3) Gecko/20030312

I am developing web pages using heavy CSS and xhtml. When I test a change to my
html Mozilla won't recognize that the page has changed. I have to go to
Preferences and dump the cache before it will see the change. 

Reproducible: Always

Steps to Reproduce:
1. Make a change to html
2. attampt to display
3. manually flush cache and retry

Actual Results:  
It works

Expected Results:  
See that the html had changed
Assignee: misc → gordon
Component: Layout: Misc Code → Networking: Cache
QA Contact: nobody → cacheqa

Comment 2

15 years ago
Warren, can you still reproduce this problem using a current nightly build? If
so, can you reproduce this problem using another Mozilla user profile?

Comment 3

15 years ago
What is your cache validation preference set to?  See Prefs -> Advanced ->
Cache.  It will be 'Everytime', 'When out of date', 'Once per session', or
'Never'.  You might also examine about:cache and look for the expiration date
HTTP cache entry for the HTML document in the disk cache.

Also, are you able to shift-reload to get the updated page without having to
clear the cache?


14 years ago
Keywords: qawanted
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.