W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2014

Re: END_SEGMENT and headers

From: David Krauss <potswa@gmail.com>
Date: Thu, 17 Apr 2014 07:33:59 +0800
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <E175F02C-A5C0-4D7B-8860-50F8D2C03CF5@gmail.com>
To: Roberto Peon <grmocg@gmail.com>
No, I’m going purely by the HTTP2 spec. A HEADERS frame must initiate a new stream, and a CONTINUATION frame must be preceded on the connection by a HEADERS or CONTINUATION frame from the same stream.

On 2014–04–17, at 7:32 AM, Roberto Peon <grmocg@gmail.com> wrote:

> Are you mixing up the HTTP on HTTP2 usecase with the framing part of HTTP2?
> -=R
> On Wed, Apr 16, 2014 at 4:30 PM, David Krauss <potswa@gmail.com> wrote:
> You mean all on the same stream? No, that is not allowed, because the headers (and CONTINUATIONs) must be an uninterrupted sequence of frames. There must be exactly one HEADERS frame per stream because it changes the stream’s state.
> Before the headers are complete, the server cannot dispatch the stream to an application, so there is no application there to receive the metadata…

Received on Wednesday, 16 April 2014 23:34:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:30 UTC