IETF Logo Mail Archive

Re: Is the response header "Upgrade: h2" allowed when TLS is used?

Daniel Stenberg <daniel@haxx.se> Tue, 19 April 2016 16:05 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@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 11AD212D8F7 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 19 Apr 2016 09:05:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.917
X-Spam-Level:
X-Spam-Status: No, score=-7.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 rIu0q-XgBcEE for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 19 Apr 2016 09:05:46 -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 1034812E19B for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 19 Apr 2016 09:05:45 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1asY5L-0004KQ-SI for ietf-http-wg-dist@listhub.w3.org; Tue, 19 Apr 2016 16:01:07 +0000
Resent-Date: Tue, 19 Apr 2016 16:01:07 +0000
Resent-Message-Id: <E1asY5L-0004KQ-SI@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <daniel@haxx.se>) id 1asY5I-0004Hq-AP for ietf-http-wg@listhub.w3.org; Tue, 19 Apr 2016 16:01:04 +0000
Received: from giant.haxx.se ([80.67.6.50] ident=root) by lisa.w3.org with esmtp (Exim 4.80) (envelope-from <daniel@haxx.se>) id 1asY5F-0000zb-Su for ietf-http-wg@w3.org; Tue, 19 Apr 2016 16:01:03 +0000
Received: from giant.haxx.se (dast@localhost.localdomain [127.0.0.1]) by giant.haxx.se (8.15.2/8.15.2/Debian-3) with ESMTPS id u3JG0b0c021775 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 19 Apr 2016 18:00:37 +0200
Received: from localhost (dast@localhost) by giant.haxx.se (8.15.2/8.15.2/Submit) with ESMTP id u3JG0aCU021772; Tue, 19 Apr 2016 18:00:36 +0200
X-Authentication-Warning: giant.haxx.se: dast owned process doing -bs
Date: Tue, 19 Apr 2016 18:00:36 +0200
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Cory Benfield <cory@lukasa.co.uk>
cc: Lucas Pardue <Lucas.Pardue@bbc.co.uk>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
In-Reply-To: <BE75D624-3A89-463A-B860-A2E83613C199@lukasa.co.uk>
Message-ID: <alpine.DEB.2.20.1604191756270.6220@tvnag.unkk.fr>
References: <20160419161634.Horde.7_VYZk5McZE4CAiQrQh-uXr@webmail.michael-kaufmann.ch> <7CF7F94CB496BF4FAB1676F375F9666A2A7CBD72@bgb01xud1012> <BE75D624-3A89-463A-B860-A2E83613C199@lukasa.co.uk>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="1129329158-1558075597-1461081636=:6220"
Received-SPF: pass client-ip=80.67.6.50; envelope-from=daniel@haxx.se; helo=giant.haxx.se
X-W3C-Hub-Spam-Status: No, score=-6.7
X-W3C-Hub-Spam-Report: AWL=0.505, BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1asY5F-0000zb-Su 0960ffab0b55071ca9851b3296f7d8b9
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Is the response header "Upgrade: h2" allowed when TLS is used?
Archived-At: <http://www.w3.org/mid/alpine.DEB.2.20.1604191756270.6220@tvnag.unkk.fr>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/31508
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>

On Tue, 19 Apr 2016, Cory Benfield wrote:

>> Stefan and Daniel point out that the server uses the Upgrade header to 
>> "advertise support" for h2.
>
> I don’t think that’s really a good way to read this section of RFC 7230.

I'd like to point out that my argument in that report was when the client in 
question originally took the Upgrade: response header as some sort of 
instruction of what to do next, while I'm saying Upgrade: in a response header 
is only an advertisement for support - not an instruction to do anything. I 
said that disregarding the actual protocol it mentioned.

I think Upgrade: should probably say h2c as a h2 in there begs the question 
what that really means...

-- 

  / daniel.haxx.se

v2.23.0 | Report a Bug | By Email