251304 - does not honor "Expires" and "Cache-Control: no-cache" headers

Status: RESOLVED EXPIRED

(Core :: Networking: HTTP, defect)

Description

[Alexander Beyn]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040614 Firefox/0.9
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040614 Firefox/0.9

When reloading a page, Firefox does not seem to honor the "Cache-Control:
no-cache" and the "Expires" headers. The server sets these, but Firefox happily
uses the cached version. The server does respond with a "304 Not Modified"
status, but I was under the impression the Expires/Cache-control headers would
still clear the cache.

The server has changed IP addresses, though not hostnames, between the time the
page was cached and now.

Reproducible: Always
Steps to Reproduce:
(this was the sequence of events, not necessarily how to reproduce)
1) Create website on ipaddressA, with "hostname" pointing to ipaddressA
2) go to "hostname" from firefox
3) change "hostname" to point to ipaddressB, which hosts another site,
responding as described above
4) go to "hostname" from firefox
5) notice old site. reload.

Actual Results:  
firefox continued pulling the page contents from cache, instead of loading from
the server

Expected Results:  
Firefox should have invalidated the local cache and pulled the page from the server

Comment 1

[Alexander Beyn]

Attachment: tcpdump of reloading the page in question twice

Comment 2

[Frank Wein [:mcsmurf]]

Maybe dupe of Bug 254353?

Comment 3

[Ken Johanson]

Possibly related to bug#204860 and bug#203271; Though both Expires and
Last-Modified are not working for me..

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.