Open Bug 1348703 Opened 8 years ago Updated 2 years ago

Overachieving cache invalidation

Categories

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

Product:
Core
Component:
Networking: Cache
Version:
55 Branch
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: mnot, Unassigned)

Details

(Whiteboard: [necko-backlog])

In Bug #327765, cache invalidation upon an unsafe request was implemented. I have new tests here: Firefox is by far the most conformant browser. However, it does fail one test -- when the unsafe request's response status code is not successful (2xx or 3xx), it still invalidates the cache. This is not really a spec conformance issue (being a cache, it can drop a stored response on the floor whenever it wants); just logging it here for completeness (and the fix is *probably* pretty easy). Relevant spec text: http://httpwg.org/specs/rfc7234.html#invalidation Test: https://github.com/mnot/web-platform-tests/blob/http-cache/fetch/http-cache/invalidate.html
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
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.