Closed
Bug 701188
Opened 13 years ago
Closed 9 years ago
Suboptimal use of cache-space for partial cache-entries with content-encoding
Categories
(Core :: Networking: Cache, defect)
Core
Networking: Cache
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: bjarne, Unassigned)
Details
Bug #612135 disabled range-requests for partially cached entries with content-encoding in a way which IMO is suboptimal (and may open up for more subtle bugs). The sub-optimality is because nsHttpChannel::CloseCacheEntry() may leave cached partial entries which will never be re-used, because nsHttpResponseHead::IsResumable() can return true while nsHttpChannel::CheckCache() may not reuse it if it's content-encoded.
![]() |
||
Comment 1•13 years ago
|
||
I think this is as well as bug 613159 dependent on the real usage numbers.
Reporter | ||
Comment 2•13 years ago
|
||
The fix is pretty simple: Modify nsHttpResponseHead::IsResumable() to also include a check for content-encoding. That way, nsHttpResponseHead::IsResumable() returns *our* view on whether the response is resumable or not, and not just the definition from the Rfc.
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•