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

Re: CONTINUATION frames on half-closed streams?

From: Joe DeVivo <joe@devivo.com>
Date: Thu, 28 Jan 2016 22:14:00 +0000
To: Martin Thomson <martin.thomson@gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <CAPPWZjkpgxbunDsAWZpz17Be31xrb=wW5LXBOae-1brjJn+Z8Q@mail.gmail.com>
That makes perfect sense, and means less work for me :D 


On Thu, Jan 28, 2016 at 3:12 PM, Martin Thomson <martin.thomson@gmail.com <mailto:martin.thomson@gmail.com>> wrote:
On 29 January 2016 at 07:40, Joe DeVivo <joe@devivo.com <mailto:joe@devivo.com>> wrote:
> But, the two statements above make me think that a half-closed stream could
> also send one or more CONTINUATION frames if it first sends a HEADERS frame
> with the END_STREAM flag set, but not the END_HEADERS flag set.

Here's how to think of it (and this is in your first quote):  A
CONTINUATION frame is just part of the previous HEADERS frame.  The
stream is only half-closed AFTER the frame is completely sent, which
includes any CONTINUATION frames.

Note that Section 5.1 also says:

> In this regard, CONTINUATION frames do not result in state transitions; they are effectively part of the HEADERS or PUSH_PROMISE that they follow. For the purpose of state transitions, the END_STREAM flag is processed as a separate event to the frame that bears it; a HEADERS frame with the END_STREAM flag set can cause two state transitions.
Received on Friday, 29 January 2016 07:47:01 UTC

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