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

Re: Issue #154: Sending a response before the request is complete

From: Roberto Peon <grmocg@gmail.com>
Date: Fri, 28 Jun 2013 22:41:19 -0700
Message-ID: <CAP+FsNfG7=mS_b-7tPrM_zDXefwa9xno64VkX4ranCDp4tTJsg@mail.gmail.com>
To: James M Snell <jasnell@gmail.com>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
I could see adding a blurb which states that headers are not complete
unless they're complete, but otherwise, this is HTTPbis as opposed to
HTTP/2 material, I think?

On Fri, Jun 28, 2013 at 10:35 PM, James M Snell <jasnell@gmail.com> wrote:

> https://github.com/http2/http2-spec/issues/154
> Suggested add to the HTML mapping...
> ---
> The server MUST NOT begin sending the response header block
> until it receives all of the request headers from the
> client; however, the server MAY begin sending the response
> immediately after receiving the request headers without waiting
> for the complete request payload or trailers to be received.
> ---
> Since we added HEADER continuations, there is a risk that a server
> might begin its response to a request prematurely, without waiting for
> the complete set of headers to be received. Doing so could cause quite
> a few major issues including caching problems.
> While this is not something that we can strictly enforce as a MUST, it
> is something that servers really ought to do.
Received on Saturday, 29 June 2013 05:41:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:13 UTC