There are scenarios we re-validate with the server (actually go to the server) based on expiration time. However, in those cases there is no way to build any conditional request headers (no Last-Modified, no ETag in the response, no If-* custom request header as well). Hence, we never get 304 for such a request. Still, we block any waiting consumers for the same cache entry for such entries with returning ENTRY_NEEDS_REVALIDATION from nsHttpChannel::OnCacheEntryCheck. Instead returning ENTRY_NEEDS_REVALIDATION when mDidReval is set, better do so only when any If-* header is set. We are anyway going to recreate the cache entry after a non-304 response.
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.