[Webkit-unassigned] [Bug 172646] Abort HTTP/2 push streams if the item is already in the HTTP cache

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=172646

--- Comment #3 from Jake Archibald <jaffathecake at gmail.com> ---
I agree the spec isn't clear when the push should be cancelled. There's some discussion of this in the Chrome issue, eg https://bugs.chromium.org/p/chromium/issues/detail?id=232040#c62

Personally, it enters a grey area when the pushed resource is clearly fresher than the item in the HTTP cache (from last-modified or etag headers).

However, it seems pretty clear-cut if the pushed item has the same last-modified/etag header as the item in the HTTP cache - continuing to receive this is a waste of bandwidth.

If the item in the cache is fresh, and it isn't clear if the pushed item is fresher, rejecting the stream still feels like the right thing to do, as HTTP/1 users would use the cached item.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170527/bed412a6/attachment-0001.html>