Closed Bug 204684 Opened 22 years ago Closed 19 years ago

Expires header appears not to affect browser behavior

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED EXPIRED

People

(Reporter: sbayne, Assigned: darin.moz)

Details

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 Dynamic pages (PHP/apache v1x, apache v2x) that send valid Expires: http headers are still coming from cache. (even when "compare every time I view the page" is set in cache preferences). Also, the page info dialog indicates that there is no Expires header being set. Here's an example header line, pulled from netcat: "Expires: Mon, 4 Jan 1999 12:00:00 GMT". IE has no problem, and always gets a current version of the page. Reproducible: Always Steps to Reproduce: 1.go to db-generated page 2.change underlying data 3. go to same page again, note that page hasn't changed. Actual Results: see above. Expected Results: 1. should notice that page has expired, and reload from network instead of cache. 2. Page info "Expires" field should be accurate
I observed the same behaviour (only <shift>-reload produces a new page, reload itself shows the cached page) with Firebird 0.7. Here is the header of the page. <head> <meta http-equiv="content-type" content="text/html;charset=ISO-8859-1"> <meta name="generator" content="Adobe GoLive 5"> <meta http-equiv="pragma" content="no-cache"> <meta http-equiv="Cache-Control" content="no-cache, must-revalidate"> <meta http-equiv="Expires" content="Mon, 15 Jan 2000 05:00:00 GMT"> <meta http-equiv="Last-Modified" content="Mon, 20 Oct 2003 10:07:02 GMT"> <title>Test Run Results</title> <link href="xxx/xxx.css" rel="stylesheet"> </head>
This bug does not occur on Linux with Firebird 0.7
I got a request from some guy that this affected windows machines as well, but not linux.
OS: MacOS X → All
Hardware: Macintosh → All
Possibly related to bug#204860 and bug#203271; Though both Expires and Last-Modified not acknowledged for me..
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.