IETF Logo Mail Archive

Re: HTTP 2.0 "Upgrade" flow

Roberto Peon <grmocg@gmail.com> Wed, 17 April 2013 06:40 UTC

Return-Path: <ietf-http-wg-request@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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B461721F85DB for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 16 Apr 2013 23:40:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SGNo8B6HeknL for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 16 Apr 2013 23:40:51 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 1847D21F8598 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 16 Apr 2013 23:40:51 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1USM2M-00035L-L1 for ietf-http-wg-dist@listhub.w3.org; Wed, 17 Apr 2013 06:40:10 +0000
Resent-Date: Wed, 17 Apr 2013 06:40:10 +0000
Resent-Message-Id: <E1USM2M-00035L-L1@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <grmocg@gmail.com>) id 1USM2J-00034H-9b for ietf-http-wg@listhub.w3.org; Wed, 17 Apr 2013 06:40:07 +0000
Received: from mail-oa0-f42.google.com ([209.85.219.42]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <grmocg@gmail.com>) id 1USM2I-0005uf-En for ietf-http-wg@w3.org; Wed, 17 Apr 2013 06:40:07 +0000
Received: by mail-oa0-f42.google.com with SMTP id i18so1281339oag.29 for <ietf-http-wg@w3.org>; Tue, 16 Apr 2013 23:39:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=VH2xGnWpvheTeo23LZS6xmcFZYIO3N6vF/sbuN9yTTA=; b=sXYBZDWe7v2kLiph8MGWVRSwA08FwWvjOD05AcWmSXu2m3KyaY4GbHoQsEW7nGqoQl 4LpIhiXdxqEAaqhGXDSAg2RiSRUT1vL7dms+SHPIqmDdUTwClrIs7JS95xnD9fTIRvDQ 2uEprLh7D4UQlD3MxD0U3CzYPh2akqmyj7BbhS7L8PdHM3cEP8z5jAi+1gc6tZa2xMoQ ur5A0t7ic1yQuyMSFkQA7mauLx8lsHQg83dGr7YgYBIy2jACOrY6f2OOrFBoDvPUF3NP XLRVUDikrgMX9+JidLARRj4Y8Z6rMNxApN+LeRMvvRqfrGiZc7cmAoTh4lj5Lnllj7+A aS/g==
MIME-Version: 1.0
X-Received: by 10.182.128.105 with SMTP id nn9mr1993156obb.10.1366180465674; Tue, 16 Apr 2013 23:34:25 -0700 (PDT)
Received: by 10.76.141.83 with HTTP; Tue, 16 Apr 2013 23:34:25 -0700 (PDT)
In-Reply-To: <20130417062716.GM5516@1wt.eu>
References: <CAKRe7JGk2496QPTZ7POqZtA4e5Gb5zs3BfJMdKveYnrK+LDe3g@mail.gmail.com> <em352963fa-7040-4466-8bd5-5e480f58e35b@bombed> <CAP+FsNcrChWevfdwNgr0e=GH5xKqLYmTjRkffrdM+HvXFtwL+Q@mail.gmail.com> <20130417062716.GM5516@1wt.eu>
Date: Tue, 16 Apr 2013 23:34:25 -0700
Message-ID: <CAP+FsNc7szKkwTz8Oz8xtDoYgWf-uyH0fpe59W5+Dd4Cj4CrQw@mail.gmail.com>
From: Roberto Peon <grmocg@gmail.com>
To: Willy Tarreau <w@1wt.eu>
Cc: "Adrien W. de Croy" <adrien@qbik.com>, Ilya Grigorik <ilya@igvita.com>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>, Ilari Liusvaara <ilari.liusvaara@elisanet.fi>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="e89a8ff1cf6c5b0f9004da88ad12"
Received-SPF: pass client-ip=209.85.219.42; envelope-from=grmocg@gmail.com; helo=mail-oa0-f42.google.com
X-W3C-Hub-Spam-Status: No, score=-3.4
X-W3C-Hub-Spam-Report: AWL=-2.625, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1USM2I-0005uf-En a95f1ac9af1be85c2cef2128cbcd1e71
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP 2.0 "Upgrade" flow
Archived-At: <http://www.w3.org/mid/CAP+FsNc7szKkwTz8Oz8xtDoYgWf-uyH0fpe59W5+Dd4Cj4CrQw@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17285
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>

Yup. The question there is only how we can do a reasonably effective
fast-fail with minimal effort.
-=R


On Tue, Apr 16, 2013 at 11:27 PM, Willy Tarreau <w@1wt.eu> wrote:

> Hi Roberto,
>
> On Tue, Apr 16, 2013 at 10:18:54PM -0700, Roberto Peon wrote:
> > As proposed by Gabriel, SETTINGS (or equivalent) would/could be carried
> in
> > the headers in the UPGRADE request.
> > However, this isn't enough by itself-- you still want to cause
> transparent
> > proxies to barf when you start speaking HTTP/2 if they're not going to be
> > able to handle it.
>
> However if the client knows from a previous connection that HTTP/2 is
> supported as an upgrade along the path, it can safely send its settings
> next to the headers, just as some browsers do with CONNECT requests sent to
> proxies. If a transparent proxy fails on this, it means it tried to parse
> the data following the headers as a new HTTP request, which means it's not
> compatible with the Upgrade mechanism anyway.
>
> Willy
>
>

v2.23.0 | Report a Bug | By Email