Open
Bug 1925456
Opened 1 year ago
Updated 11 months ago
Consider not failing the HTTP channel if the revalidation network request fails
Categories
(Core :: Networking: Cache, enhancement, P2)
Core
Networking: Cache
Tracking
()
NEW
People
(Reporter: valentin, Unassigned)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [necko-triaged][necko-priority-next])
Attachments
(1 file)
While looking at some logs in bug 1896216 I noticed that we had a cache entry for a request that we needed to revalidate.
However, the network request failed, so the channel failed.
I think we should consider whether it's correct to continue the load from cache like we would do when receiving a 304 not modified or when the browser is offline.
|
Reporter | |
Updated•1 year ago
|
Summary: Consider not failing the request if the revalidation channel fails → Consider not failing the HTTP channel if the revalidation network request fails
|
||
Comment 1•1 year ago
|
||
This seems like it would be a clear win for the user experience when transitioning out of a network.
Whiteboard: [necko-triaged][necko-priority-new] → [necko-triaged][necko-priority-next]
|
|
Reporter | |
Comment 3•1 year ago
|
||
|
|
Reporter | |
Comment 4•1 year ago
|
||
|
||
Updated•11 months ago
|
Points: --- → 2
Rank: 3
Flags: needinfo?(rjesup)
You need to log in
before you can comment on or make changes to this bug.
Description
•