- From: Patrick McManus <pmcmanus@mozilla.com>
- Date: Thu, 23 Oct 2014 15:46:48 -0400
- To: HTTP Working Group <ietf-http-wg@w3.org>
- Message-ID: <CAOdDvNq0Wfo-VxYx47agrRAh7YnmEkbacB7HZ6pOuFNB1k_Dtg@mail.gmail.com>
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 <http://http2.github.io/http2-spec/index.html#PRIORITY> frame MAY be received in this state. Receiving any type of frame other than RST_STREAM <http://http2.github.io/http2-spec/index.html#RST_STREAM> or PRIORITY <http://http2.github.io/http2-spec/index.html#PRIORITY> on a stream in this state MUST be treated as a connection error (Section 5.4.1 <http://http2.github.io/http2-spec/index.html#ConnectionErrorHandler>) of type PROTOCOL_ERROR <http://http2.github.io/http2-spec/index.html#PROTOCOL_ERROR>. * point to node! However it also has this to say: *reserved (remote): [..]* *An endpoint MAY send a PRIORITY <http://http2.github.io/http2-spec/index.html#PRIORITY> frame in this state to reprioritize the reserved stream. An endpoint MUST NOT send any type of frame other than RST_STREAM <http://http2.github.io/http2-spec/index.html#RST_STREAM>, WINDOW_UPDATE <http://http2.github.io/http2-spec/index.html#WINDOW_UPDATE>, or PRIORITY <http://http2.github.io/http2-spec/index.html#PRIORITY> in this state. * point to firefox! We're all winners here. Which state should be changed? -Patrick
Received on Thursday, 23 October 2014 19:47:11 UTC