Subject: [quicwg/base-drafts] Rationalise HTTP_WRONG_STREAM and HTTP_UNEXPECTD_FRAME (#2809)

From: Lucas Pardue <[email-masked]>
Date: Wed, 19 Jun 2019 03:31:41 -0700

HTTP_WRONG_STREAM and HTTP_UNEXPECTED_FRAME are used a lot and very
similar. The former is used by a peer that receives a valid frame on a
stream that it should never be sent on, the latter is used by a peer
that receives a valid frame on a stream that is normally ok but has
transitioned to an application-level stream state which prohibits it.
Rationalising these seems like a logical option.

-- 
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/2809