Closed Bug 1368661 Opened 8 years ago Closed 8 years ago

HTTP/2 push streams should be cancelled if the item is already in the HTTP cache

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1367551

People

(Reporter: jaffathecake, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce: I have a scrappy test at https://github.com/jakearchibald/http2-push-test/. Once the server is running, visit /, fetch the pushed item into the cache, then refresh the page to receive the push again. Actual results: Firefox allows the push to continue. Expected results: Cancel the push – it isn't needed. Chrome is getting ready to ship this https://bugs.chromium.org/p/chromium/issues/detail?id=232040, and as far as I can tell, Edge already shipped it.
Component: Untriaged → Networking: HTTP
Product: Firefox → Core
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Ugh, sorry I missed the other issue. Maybe I searched for "HTTP/2", or maybe I'm just dumb.
(In reply to Jake Archibald from comment #2) > Ugh, sorry I missed the other issue. Maybe I searched for "HTTP/2", or maybe > I'm just dumb. Its ok. Its better to have 2 bugs instead of 0 bugs.
You need to log in before you can comment on or make changes to this bug.