Open Bug 802915 Opened 12 years ago Updated 3 years ago

Recover from cache entry opening/reading failures when it isn't too late by fetching the response from the net

Categories

(Core :: Networking: HTTP, defect, P5)

Product:
Core
Component:
Networking: HTTP
Type:
defect

Tracking

()

People

(Reporter: briansmith, Unassigned)

Details

(Whiteboard: [necko-backlog]) 

+++ This bug was initially created as a clone of Bug #771832 +++

See bug 771832 comment 25. Basically, if we encounter any problem reading a cache entry before we start returning data from it, we should treat that failure like a revalidation failure: doom the cache entry, and fetch the resource from the network. See bug 746018, which implements part of this.
Note also that maybe a better solution is to change the users of nsIHttpChannel so *they* implement the retry logic. That way, we could handle these failures even after the channel has returned data to the user of the channel.
Summary: File not found error for HTTP URL, can be fixed by a forced reload → Recover from cache entry opening/reading failures when it isn't too late by fetching the response from the net
Whiteboard: [necko-backlog]
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3

Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.

Severity: major → S4
Priority: P3 → P5
You need to log in before you can comment on or make changes to this bug.