- From: Mark Nottingham <mnot@mnot.net>
- Date: Fri, 24 Oct 2014 11:07:47 +1100
- To: Patrick McManus <pmcmanus@mozilla.com>, HTTP Working Group <ietf-http-wg@w3.org>
Thanks Patrick, created as <https://github.com/http2/http2-spec/issues/634>. It sounds like so far, people agree we should update reserved (local). Anyone disagree? Cheers, > On 24 Oct 2014, at 6:46 am, Patrick McManus <pmcmanus@mozilla.com> wrote: > > Hi All. > > Firefox receives a PUSH_PROMISE from node-http2 (speaking -14). That puts Firefox into reserved-remote and node into reserved-local. > > Firefox sends a WINDOW_UPDATE on that stream and node replies with GOAWAY Protocol-Error > > Section 5.1 of -14 has this to say: > reserved (local): [..] > A PRIORITY frame MAY be received in this state. Receiving any type of frame other than RST_STREAM or PRIORITY on a stream in this state MUST be treated as a connection error (Section 5.4.1) of type PROTOCOL_ERROR. > > point to node! However it also has this to say: > > reserved (remote): [..] > An endpoint MAY send a PRIORITY frame in this state to reprioritize the reserved stream. An endpoint MUST NOT send any type of frame other than RST_STREAM, WINDOW_UPDATE, or PRIORITY in this state. > > point to firefox! We're all winners here. > > Which state should be changed? > > > -Patrick > > > > > > > -- Mark Nottingham https://www.mnot.net/
Received on Friday, 24 October 2014 00:08:14 UTC