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

James M Snell <jasnell@gmail.com> Sat, 29 June 2013 05:36 UTC

Resent-Date: Sat, 29 Jun 2013 05:36:21 +0000
Resent-Message-Id: <E1Usnpd-0001oJ-Mt@frink.w3.org>
MIME-Version: 1.0
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>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=209.85.214.179; envelope-from=jasnell@gmail.com; helo=mail-ob0-f179.google.com
Subject: Issue #154: Sending a response before the request is complete
Archived-At: <http://www.w3.org/mid/CABP7RbcAWkm9uqkQt2dsYYnHw40ax7mM7GEjLDE8uBn4pn-4Pg@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

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.

Issue #154: Sending a response before the request… James M Snell
Re: Issue #154: Sending a response before the req… Roberto Peon
Re: Issue #154: Sending a response before the req… James M Snell
Re: Issue #154: Sending a response before the req… Jeff Pinner
Re: Issue #154: Sending a response before the req… Martin Thomson
Re: Issue #154: Sending a response before the req… Roberto Peon