Closed
Bug 114286
Opened 24 years ago
Closed 24 years ago
No way to determine if a http request was a 304 or not.
Categories
(Core :: Networking: HTTP, defect, P3)
Tracking
()
RESOLVED
FIXED
mozilla0.9.8
People
(Reporter: pavlov, Assigned: darin.moz)
References
Details
(Whiteboard: [ready to land])
Attachments
(1 file)
|
3.03 KB,
patch
|
pavlov
:
review+
mscott
:
superreview+
|
Details | Diff | Splinter Review |
There is no way to figure out if a http request got a 304 response, because in
nsHttpChannel::ProcessNotModified(), it deletes mResponseHead (which had 304
set on it) and replaces it with mCachedResponseHead which has 200 set. It then
proceeds to set mCachedContentIsValid, which is really what I want access to.
| Assignee | ||
Comment 1•24 years ago
|
||
exposing mCachedContentIsValid would give you only 304 cases, but any case when
the cache is being read. this is probably sufficient for what imglib needs, right?
| Reporter | ||
Updated•24 years ago
|
Keywords: mozilla0.9.8
| Assignee | ||
Updated•24 years ago
|
Priority: -- → P3
Target Milestone: --- → mozilla0.9.8
| Assignee | ||
Comment 2•24 years ago
|
||
this patch does two things:
1) adds nsICachingChannel::isFromCache() method to indicate whether or not a
channel's data is coming from the cache.
2) makes nsHttpChannel not discard its cache entry when canceled if its cache
entry is simply being read.
| Assignee | ||
Comment 3•24 years ago
|
||
pavlov: does this do the trick for you? if so, can i get an r=? thx!
| Reporter | ||
Comment 4•24 years ago
|
||
Comment on attachment 61526 [details] [diff] [review]
v1.0 patch
r=pavlov
Attachment #61526 -
Flags: review+
Comment 5•24 years ago
|
||
Comment on attachment 61526 [details] [diff] [review]
v1.0 patch
sr=mscott
Attachment #61526 -
Flags: superreview+
| Assignee | ||
Updated•24 years ago
|
Whiteboard: [ready to land]
| Assignee | ||
Comment 6•24 years ago
|
||
fixed-on-trunk
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•