W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2015

Re: HTTP/2 Upgrade with content?

From: Daniel Stenberg <daniel@haxx.se>
Date: Fri, 13 Mar 2015 08:40:02 +0100 (CET)
To: Stefan Eissing <stefan.eissing@greenbytes.de>
cc: Greg Wilkins <gregw@intalio.com>, Mike Bishop <Michael.Bishop@microsoft.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <alpine.DEB.2.11.1503130833190.13706@tvnag.unkk.fr>
On Fri, 13 Mar 2015, Stefan Eissing wrote:

> - hear from clients what they prefer/expect. there could be a response 
> header "upgrade: no-conten" or such

Not accepting a POST immediately will be surprising to users. There are quite 
a few users in the wild today that run curl like this:

  $ curl -d lotsofdata [URL]

which thus sends a POST immediately with that data over HTTP/1.1, and the same 
thing for HTTP/2 is almost identical, just adding asking for http2:

  $ curl --http2 -d lotsofdata [URL]

which will make a POST with an Upgrade: h2c header and Expect: 100-continue.

If a server then suddenly doesn't handle the POST + upgrade it puts a rather 
arbitrary (from the client's perspective) block on when a client can or 
cannot switch to HTTP/2 on such a server.


  / daniel.haxx.se
Received on Friday, 13 March 2015 07:40:32 UTC

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