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

Re: Expect: + Upgrade: = ...

From: Roy T. Fielding <fielding@gbiv.com>
Date: Thu, 5 Sep 2013 11:17:02 -0700
Cc: Daniel Stenberg <daniel@haxx.se>, Amos Jeffries <squid3@treenet.co.nz>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <B97C5E3A-819B-407F-81F3-236FBF1086D3@gbiv.com>
To: Michael Sweet <msweet@apple.com>
On Sep 5, 2013, at 10:17 AM, Michael Sweet wrote:

> On Sep 5, 2013, at 12:17 PM, Daniel Stenberg <daniel@haxx.se> wrote:
>> On Thu, 5 Sep 2013, Roy T. Fielding wrote:
>> 
>>> In any case, it is very unlikely that a client's first request to a server is a big POST.
>> 
>> For a browser sure. For curl and libcurl users that's a fairly common use case. Or at least not a rare one.
> 
> and for CUPS and IPP...

which, again, will gain nothing from switching to HTTP/2 before
the initial request body is sent.

Using both Expect: 100-continue and Upgrade, at the same time,
will work fine -- it can be implemented as already specified.
100 is required to be sent first.

....Roy
Received on Thursday, 5 September 2013 18:17:22 UTC

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