Re: HTTP/2 Upgrade with content?

Stefan Eissing <stefan.eissing@greenbytes.de> Sat, 14 March 2015 08:12 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 865AA1AC447 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 14 Mar 2015 01:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, 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 WurhfMbsKflU for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 14 Mar 2015 01:12:16 -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 70B021AC42E for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sat, 14 Mar 2015 01:12:16 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1YWh6y-0002kM-Q2 for ietf-http-wg-dist@listhub.w3.org; Sat, 14 Mar 2015 08:07:56 +0000
Resent-Date: Sat, 14 Mar 2015 08:07:56 +0000
Resent-Message-Id: <E1YWh6y-0002kM-Q2@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 1YWh6o-0002hm-4y for ietf-http-wg@listhub.w3.org; Sat, 14 Mar 2015 08:07:46 +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 1YWh6m-0001jO-It for ietf-http-wg@w3.org; Sat, 14 Mar 2015 08:07:46 +0000
Received: from [192.168.178.31] (unknown [84.150.88.6]) (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 AA57E15A046F; Sat, 14 Mar 2015 09:07:21 +0100 (CET)
Content-Type: multipart/alternative; boundary="Apple-Mail-A384ABED-88E1-42C6-A6F1-3DB3A731FEC7"
Mime-Version: 1.0 (1.0)
From: Stefan Eissing <stefan.eissing@greenbytes.de>
X-Mailer: iPhone Mail (12D508)
In-Reply-To: <CAH_y2NG-WLGKJ+gZrrV+0tkSQ0gdR9RETCo1R9xZvHJTkRWO5g@mail.gmail.com>
Date: Sat, 14 Mar 2015 09:07:20 +0100
Cc: Daniel Stenberg <daniel@haxx.se>, "Jason T. Greene" <jason.greene@redhat.com>, Mike Bishop <Michael.Bishop@microsoft.com>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Transfer-Encoding: 7bit
Message-Id: <BB0E98C7-2D88-42B7-AF89-AE320057E907@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> <6E036F2D-AED0-4323-ACCB-D8036168E6C1@redhat.com> <CAH_y2NFjb0mx8Rs+qg6uJ=zgUzHW3ksiOSN4_GXubKG-P2QDaw@mail.gmail.com> <alpine.DEB.2.11.1503131457030.27951@tvnag.unkk.fr> <B6CAD842-64A1-4D7B-839C-852AF5AAD221@greenbytes.de> <CAH_y2NG-WLGKJ+gZrrV+0tkSQ0gdR9RETCo1R9xZvHJTkRWO5g@mail.gmail.com>
To: Greg Wilkins <gregw@intalio.com>
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.6
X-W3C-Hub-Spam-Report: AWL=-2.618, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RP_MATCHES_RCVD=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001
X-W3C-Scan-Sig: lisa.w3.org 1YWh6m-0001jO-It ab440900cb3b6391054d9159afcf66a1
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP/2 Upgrade with content?
Archived-At: <http://www.w3.org/mid/BB0E98C7-2D88-42B7-AF89-AE320057E907@greenbytes.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/28972
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>

Greg,

totally agree. That is what mod_h2 is already doing and it will stay that way. It does also upgrade on any suitable request, not only the first. 



> Am 13.03.2015 um 23:21 schrieb Greg Wilkins <gregw@intalio.com>:
> 
> 
>> On 14 March 2015 at 01:21, Stefan Eissing <stefan.eissing@greenbytes.de> wrote:
>> - maybe a mixed 1.1 up and h2c down request could be made to work, but there seems no gain for anyone in creating this mythical beast.
> 
> Stefan,
> 
> it would not be impossible to implement this - except I see there is no way around the risk of deadlock if up is streamed or the DoS issue if up is held in memory.
> 
> So rather than encourage a false belief that such a mechanism might work for arbitrary content, I think it is better for servers to ignore all upgrades with any content.
> 
> cheers
> 
> 
> 
> 
> -- 
> Greg Wilkins <gregw@intalio.com>  @  Webtide - an Intalio subsidiary
> http://eclipse.org/jetty HTTP, SPDY, Websocket server and client that scales
> http://www.webtide.com  advice and support for jetty and cometd.