Closed
Bug 383538
Opened 18 years ago
Closed 9 years ago
occasionally when trying to reload particular feed as a livemark, we see cache expiration time of 0
Categories
(Core :: Networking: Cache, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: moco, Unassigned)
References
()
Details
occasionally when trying to reload particular feed as a livemark, we see cache expiration time of 0
looking at nsHttpChannel::UpdateExpirationTime(), could this be caused by mResponseHead->MustValidate() returning false, and so we call mCacheEntry->SetExpirationTime() with 0?
I'll try to make this happen in the debugger to figure out why the expiration time might be 0.
Note, see http://lxr.mozilla.org/mozilla/source/toolkit/components/places/src/nsLivemarkService.js#213 for how we create this http request.
Reporter | ||
Comment 1•18 years ago
|
||
note, the feed we are seeing this with is:
http://rss.cnn.com/rss/cnn_latest.rss
Reporter | ||
Comment 2•18 years ago
|
||
for details, see bug #357236 comment #12
Comment 3•18 years ago
|
||
This is also occasionally seen on Mac OS X as well, also tested with the cnn rss feed.
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•