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

Re: HTTP/2 response completed before its request

From: Willy Tarreau <w@1wt.eu>
Date: Tue, 1 Jul 2014 21:42:31 +0200
To: Zhong Yu <zhong.j.yu@gmail.com>
Cc: Roberto Peon <grmocg@gmail.com>, Jesse Wilson <jesse@swank.ca>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20140701194231.GE22160@1wt.eu>
On Tue, Jul 01, 2014 at 02:21:07PM -0500, Zhong Yu wrote:
> On Tue, Jul 1, 2014 at 11:45 AM, Roberto Peon <grmocg@gmail.com> wrote:
> > Getting a response before the request has finished definitely happens
> > sometimes, even in HTTP/1.1
> A server should not do that, or it will cause deadlocks with most
> major browsers.
> 100-continue is supposed to be helpful in this case, but it's not
> really adopted in practice.

I disagree, and there are a number of situations where it's quite desirable
to act like this. For example, imagine that I'm uploading a large image to
a site and my session has expired. I want the site to send the error as soon
as possible so that my browser stops emitting for nothing. I don't want it to 
wait minutes just to know that I need to re-login first then try again.

Browsers already handle this quite well in 1.1, and the real issue in fact
tends to be on the server side where it's not always easy to drain all the
request from the client after the response was sent, which sometimes results
in a TCP RST which risks to clear the response before the client has a chance
to see it. But correctly done, it's a very useful feature.

Received on Tuesday, 1 July 2014 19:42:59 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:08 UTC