Sometimes we get cache hits for cached HTTP responses that do not have the cache device set

RESOLVED WONTFIX

Status

()

Core
Networking: HTTP
RESOLVED WONTFIX
6 years ago
2 years ago

People

(Reporter: briansmith, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

I expect that when we get a cache hit, or when we attempt revalidation, that the cache entry that the cache service has passed to HttpCacheQuery::OnCacheEntryAvailable already has the cache device set. However, when I added some assertions to this affect as part of the patch for bug 763342, I found that sometimes (rarely?) we are being passed entries that do not have the cache device set, causing those assertions to fail. I haven't dug into why yet. In the patch for bug 763342, I left these assertions in the source code, commented out, with a comment referencing this bug by bug number.
cache code has been replaced
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.