IETF Logo Mail Archive

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

Michael Kaufmann <mail@michael-kaufmann.ch> Tue, 19 April 2016 14:21 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 4497512E1BF for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 19 Apr 2016 07:21:52 -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 X50_fGCRYHuB for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 19 Apr 2016 07:21:50 -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 F2F3912E15A for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 19 Apr 2016 07:21:49 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1asWSi-0004tL-NL for ietf-http-wg-dist@listhub.w3.org; Tue, 19 Apr 2016 14:17:08 +0000
Resent-Date: Tue, 19 Apr 2016 14:17:08 +0000
Resent-Message-Id: <E1asWSi-0004tL-NL@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <mail@michael-kaufmann.ch>) id 1asWSe-0004rJ-9L for ietf-http-wg@listhub.w3.org; Tue, 19 Apr 2016 14:17:04 +0000
Received: from lookie3.hostorama.com ([80.74.148.208]) by maggie.w3.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from <mail@michael-kaufmann.ch>) id 1asWSc-0005ZJ-F2 for ietf-http-wg@w3.org; Tue, 19 Apr 2016 14:17:03 +0000
Received: from lookie.metanet.ch (localhost [127.0.0.1]) by lookie3.hostorama.com (Postfix) with ESMTPSA id ADDC0AE00A9 for <ietf-http-wg@w3.org>; Tue, 19 Apr 2016 16:16:34 +0200 (CEST)
Received: from nat13.ergon.ch (nat13.ergon.ch [87.239.215.13]) by webmail.michael-kaufmann.ch (Horde Framework) with HTTP; Tue, 19 Apr 2016 16:16:34 +0200
Date: Tue, 19 Apr 2016 16:16:34 +0200
Message-ID: <20160419161634.Horde.7_VYZk5McZE4CAiQrQh-uXr@webmail.michael-kaufmann.ch>
From: Michael Kaufmann <mail@michael-kaufmann.ch>
To: ietf-http-wg@w3.org
User-Agent: Horde Application Framework 5
Content-Type: text/plain; charset="utf-8"; format="flowed"; DelSp="Yes"
MIME-Version: 1.0
Content-Disposition: inline
Received-SPF: none client-ip=80.74.148.208; envelope-from=mail@michael-kaufmann.ch; helo=lookie3.hostorama.com
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-1.399, BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, W3C_NW=0.5
X-W3C-Scan-Sig: maggie.w3.org 1asWSc-0005ZJ-F2 2403187bda980a09fc57c3a68684bd2c
X-Original-To: ietf-http-wg@w3.org
Subject: Is the response header "Upgrade: h2" allowed when TLS is used?
Archived-At: <http://www.w3.org/mid/20160419161634.Horde.7_VYZk5McZE4CAiQrQh-uXr@webmail.michael-kaufmann.ch>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/31503
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>

Hi,

I have a question regarding the "Upgrade" header. The HTTP/2  
specification says:
> A server MUST ignore an "h2" token in an Upgrade header field.  
> Presence of a token with "h2" implies HTTP/2 over TLS, which is  
> instead negotiated as described in Section 3.3.

Does this imply that a server must not (or should not) send an  
"Upgrade: h2" response header to clients?

This question is important for Apache httpd, because version 2.4.20  
sends such an "Upgrade: h2" response header to clients that speak  
HTTP/1.x. Other HTTP/2 server software does not (e.g. nginx, Google's  
and Twitter's web servers).

Related Apache httpd issue:  
https://bz.apache.org/bugzilla/show_bug.cgi?id=59311

Regards,
Michael

v2.23.0 | Report a Bug | By Email