Re: Stream state and PUSH_PROMISE

• From: Martin Thomson <martin.thomson@gmail.com>
• Date: Tue, 11 Jul 2017 10:14:50 +1000
• To: Hadil Sabbagh <hadil.sabbagh@xeia.io>
• Cc: HTTP Working Group <ietf-http-wg@w3.org>
• Message-ID: <CABkgnnW2X6FmP+P3oZSV1namM6PxZgFZMXmOVM2S9Z6x3LNphA@mail.gmail.com>

On 11 July 2017 at 09:37, Hadil Sabbagh <hadil.sabbagh@xeia.io> wrote:
> What is the state of the stream when a PUSH_PROMISE is sent or received when the stream is in the OPEN state?

Which stream is open, the stream on which the PUSH_PROMISE is sent, or
the one that is promised?

The latter case is interesting because that means that you are
sending/receiving two PUSH_PROMISE frames that promise the same stream
(and the first one has been acted upon already).  That's an error,
according to the following text from Section 5.1:

> In the absence of more specific guidance elsewhere in this document, implementations SHOULD treat the receipt of a frame that is not expressly permitted in the description of a state as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.

Received on Tuesday, 11 July 2017 00:15:22 UTC