Re: HTTP/2 Upgrade with content?

Stefan Eissing <stefan.eissing@greenbytes.de> Fri, 13 March 2015 09:19 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ietf.org@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 578961A1B67 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 13 Mar 2015 02:19:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.912
X-Spam-Level:
X-Spam-Status: No, score=-6.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fL7FCVeY3hsQ for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 13 Mar 2015 02:19:47 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 023961A1B6C for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 13 Mar 2015 02:19:47 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1YWLhm-0005nX-OR for ietf-http-wg-dist@listhub.w3.org; Fri, 13 Mar 2015 09:16:30 +0000
Resent-Date: Fri, 13 Mar 2015 09:16:30 +0000
Resent-Message-Id: <E1YWLhm-0005nX-OR@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.80) (envelope-from <stefan.eissing@greenbytes.de>) id 1YWLhf-0005mm-MT for ietf-http-wg@listhub.w3.org; Fri, 13 Mar 2015 09:16:23 +0000
Received: from mail.greenbytes.de ([217.91.35.233]) by lisa.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <stefan.eissing@greenbytes.de>) id 1YWLhd-0003S6-Rz for ietf-http-wg@w3.org; Fri, 13 Mar 2015 09:16:23 +0000
Received: from delight.greenbytes.de (unknown [217.91.35.233]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.greenbytes.de (Postfix) with ESMTPSA id B695415A05A8; Fri, 13 Mar 2015 10:15:57 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Stefan Eissing <stefan.eissing@greenbytes.de>
In-Reply-To: <alpine.DEB.2.11.1503130833190.13706@tvnag.unkk.fr>
Date: Fri, 13 Mar 2015 10:16:01 +0100
Cc: Greg Wilkins <gregw@intalio.com>, Mike Bishop <Michael.Bishop@microsoft.com>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B6F039A0-A58A-4980-9F52-F865BFFAAB0E@greenbytes.de>
References: <CAH_y2NF3iwND1ttQDY98KC_u=OZj5aqEABmXHKObMgqPH1npLg@mail.gmail.com> <BL2PR03MB1323474B977B051738AD09187060@BL2PR03MB132.namprd03.prod.outlook.com> <CAH_y2NFV=Z7hqbtWTdiePRwUnhhRjiP8R_Ua7kmpZEkwXtxgEA@mail.gmail.com> <B5C01B7A-9215-4268-B189-E6281F425BF7@greenbytes.de> <alpine.DEB.2.11.1503130833190.13706@tvnag.unkk.fr>
To: Daniel Stenberg <daniel@haxx.se>
X-Mailer: Apple Mail (2.2070.6)
Received-SPF: pass client-ip=217.91.35.233; envelope-from=stefan.eissing@greenbytes.de; helo=mail.greenbytes.de
X-W3C-Hub-Spam-Status: No, score=-3.1
X-W3C-Hub-Spam-Report: AWL=-3.112, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001
X-W3C-Scan-Sig: lisa.w3.org 1YWLhd-0003S6-Rz 43dc44cc3b95a0f6ad417445a1a34341
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP/2 Upgrade with content?
Archived-At: <http://www.w3.org/mid/B6F039A0-A58A-4980-9F52-F865BFFAAB0E@greenbytes.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/28953
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Daniel,

do you mean curl will, after seeing a 101 response, send the body on the HTTP2 stream 1? That could be made to work...

//Stefan

> Am 13.03.2015 um 08:40 schrieb Daniel Stenberg <daniel@haxx.se>:
> 
> 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

<green/>bytes GmbH
Hafenweg 16, 48155 Münster, Germany
Phone: +49 251 2807760. Amtsgericht Münster: HRB5782