Closed
Bug 142843
Opened 23 years ago
Closed 23 years ago
mozilla ignores "Expires: 0" and "Pragma: no-cache" when sent with a "Last-Modified" header
Categories
(Core :: Networking: HTTP, defect, P1)
Core
Networking: HTTP
Tracking
()
VERIFIED
FIXED
mozilla1.0
People
(Reporter: darin.moz, Assigned: darin.moz)
References
()
Details
(Keywords: regression, topembed+, Whiteboard: [RTM][fixed-trunk][m5+])
Attachments
(1 file)
|
2.59 KB,
patch
|
bbaetz
:
review+
rpotts
:
superreview+
jud
:
approval+
|
Details | Diff | Splinter Review |
mozilla ignores "Expires: 0" when sent with a "Last-Modified" header.
seems the "Last-Modified" header is causing us to calculate a non-zero freshness
lifetime... it should be trumped by the "Expires: 0", but for some reason that's
not happening.
noticed with build 2002050606 under win2k
|
Assignee | |
Updated•23 years ago
|
Status: NEW → ASSIGNED
Keywords: topembed
Priority: -- → P3
Whiteboard: [pe]
Target Milestone: --- → mozilla1.0.1
|
|
Assignee | |
Comment 1•23 years ago
|
||
actually, the same problem occurs if the server sends "pragma: no-cache" in
place of "expires: 0" ... so this seems like a major regression to me.
Severity: normal → major
Priority: P3 → P1
Whiteboard: [pe] → [pe][RTM]
Target Milestone: mozilla1.0.1 → mozilla1.0
|
|
Assignee | |
Comment 2•23 years ago
|
||
|
|
Assignee | |
Comment 3•23 years ago
|
||
(this bug is triggered on topsites like mtv.com)
|
|
Assignee | |
Updated•23 years ago
|
Summary: mozilla ignores "Expires: 0" when sent with a "Last-Modified" header → mozilla ignores "Expires: 0" and "Pragma: no-cache" when sent with a "Last-Modified" header
|
|
||
Comment 4•23 years ago
|
||
Comment on attachment 82707 [details] [diff] [review]
v1 patch
r=bbaetz
Attachment #82707 -
Flags: review+
|
|
||
Comment 5•23 years ago
|
||
Attachment #82707 -
Flags: superreview+
|
||
Comment 6•23 years ago
|
||
Please check into trunk ASAP; and if not done so already request drivers approval
|
|
||
Comment 7•23 years ago
|
||
topembed plussing this as correct caching is crucial.
|
|
||
Updated•23 years ago
|
Attachment #82707 -
Flags: approval+
|
|
||
Comment 9•23 years ago
|
||
adding adt1.0.0+. Please check into the branch as soon as possible. It looks
like Jud gave drivers approval.
|
|
Assignee | |
Comment 10•23 years ago
|
||
fixed-on-branch
|
|
||
Comment 11•23 years ago
|
||
verified on trunk - 05/09 builds winNT4, linux rh6, mac osX
|
|
||
Comment 12•23 years ago
|
||
verified on branch - 05/09 builds winNT4, linux rh6, mac osX
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•