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

CONTINUATION frames on half-closed streams?

From: Joe DeVivo <joe@devivo.com>
Date: Thu, 28 Jan 2016 20:40:32 +0000
Message-Id: <CAPPWZj=KdPcHhhBA+oN8W712M=C+8ZpsOesULaLZxt3_JZnn+g@mail.gmail.com>
To: ietf-http-wg@w3.org

Section 6.2 of RFC-7540 says:

A HEADERS frame carries the END_STREAM flag that signals the end
of a stream.  However, a HEADERS frame with the END_STREAM flag
set can be followed by CONTINUATION frames on the same stream.
Logically, the CONTINUATION frames are part of the HEADERS frame.

And Section 5.1 says under the idle stream state:

Sending or receiving a HEADERS frame causes the stream to
become "open".  The stream identifier is selected as described
in Section 5.1.1.  The same HEADERS frame can also cause a
stream to immediately become "half-closed".

Section 5.1 goes on to say under the half-closed (local) state:

A stream that is in the "half-closed (local)" state cannot be used
for sending frames other than WINDOW_UPDATE, PRIORITY, and

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.

I can read the spec both ways, so I'd appreciate some clarification.


Received on Thursday, 28 January 2016 21:39:56 UTC

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