Open Bug 763691 Opened 14 years ago Updated 5 years ago

Cached responses should be used for custom conditional requests (e.g. XMLHttpRequest requests with If-Non-Match, If-Range, If-Modified-Since, etc.) when the cached response meets the criteria of the conditional request

Categories

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

Product:
Core
Component:
Networking: Cache
Type:
defect

Tracking

()

People

(Reporter: briansmith, Unassigned)

References

(Depends on 1 open bug)

Details

(Whiteboard: [necko-backlog])

+++ This bug was initially created as a clone of Bug #759582 +++ I am planning to fix bug 759582 and related bugs by bypassing the cache completely for custom conditional requests. In order to properly process these responses by returning cached responses, we need to process the Accept, Accept-*, If-*, and other headers just like a server would. If the entry is acceptable, return the entry; ptherwise, forward the request to the network. That is what this bug is about.
Whiteboard: [necko-backlog]
Component: Networking: HTTP → Networking: Cache
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: normal → S4
Priority: P3 → P5
You need to log in before you can comment on or make changes to this bug.