W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2016

Re: Recursive HTTP/2 Push

From: Glen Knowles <gknowles@ieee.org>
Date: Tue, 9 Feb 2016 02:08:03 -0800
Message-ID: <CAJCH0yAayLSNjFtNin3Yh0J4rbqQqDN=H7b_z1Lh=qxtoG65hQ@mail.gmail.com>
To: Patrick McManus <pmcmanus@mozilla.com>
Cc: Simone Bordet <simone.bordet@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
> The spec is clear the server must not send. In general that doesn't create
> a requirement on the peer to throw a protocol_error when receiving.

In this case the spec does have an explicit requirement (section 5.1) that
a client in the "reserved (remote)" state throw a p_e.

"Receiving any type of frame other than HEADERS, RS_STREAM, or PRIORITY on
a stream in this state MUST be treated as a connection error (Section
5.4.1) of type PROTOCOL_ERROR."
Received on Tuesday, 9 February 2016 10:08:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 22 March 2016 12:47:11 UTC