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

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

From: James M Snell <jasnell@gmail.com>
Date: Fri, 28 Jun 2013 22:35:21 -0700
Message-ID: <CABP7RbcAWkm9uqkQt2dsYYnHw40ax7mM7GEjLDE8uBn4pn-4Pg@mail.gmail.com>
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>

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:36:08 UTC

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