Re: [quicwg/base-drafts] DUPLICATE_PUSH push ID validation (#2681)

[Mike Bishop <[e-mail]>]

(2) is covered in [Section 5.4](https://quicwg.org/base-drafts/draft-ietf-quic-http.html#server-push):
> Due to reordering, DUPLICATE_PUSH frames or push stream data can arrive before the corresponding PUSH_PROMISE frame. When a client receives a DUPLICATE_PUSH frame for an as-yet-unknown Push ID, the request headers of the push are not immediately available. The client can either delay generating new requests for content referenced following the DUPLICATE_PUSH frame until the request headers become available, or can initiate requests for discovered resources and cancel the requests if the requested resource is already being pushed.

For (1), yes it should -- the DUPLICATE might show up first, but the implication is that the ID has already been used in a PUSH_PROMISE frame.  If that would be invalid, we should be explicit that the DUPLICATE_PUSH is also invalid.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/2681#issuecomment-491009691