Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id CA75B200C3C for ; Mon, 3 Apr 2017 13:25:37 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C8C69160B8F; Mon, 3 Apr 2017 11:25:37 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1A72C160B76 for ; Mon, 3 Apr 2017 13:25:36 +0200 (CEST) Received: (qmail 27007 invoked by uid 500); 3 Apr 2017 11:25:36 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 26997 invoked by uid 99); 3 Apr 2017 11:25:36 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Apr 2017 11:25:36 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id AE72D1A00E3 for ; Mon, 3 Apr 2017 11:25:35 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.102 X-Spam-Level: X-Spam-Status: No, score=-0.102 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=greenbytes.de header.b=sG915QdV; dkim=pass (1024-bit key) header.d=greenbytes.de header.b=ltYty3+d Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id sxAEpJ5_DTcd for ; Mon, 3 Apr 2017 11:25:34 +0000 (UTC) Received: from mail.greenbytes.de (mail.greenbytes.de [5.10.171.186]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 34A165F397 for ; Mon, 3 Apr 2017 11:25:34 +0000 (UTC) Received: by mail.greenbytes.de (Postfix, from userid 117) id CCA5B15A2F02; Mon, 3 Apr 2017 13:25:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=greenbytes.de; s=mail; t=1491218733; bh=QuPquzsMPdIyxnh1FgJh0EC4tc5TxA5/42X7iBm+wsk=; h=From:Subject:Date:References:To:In-Reply-To:From; b=sG915QdV8oVXknIbJPAWzsFmlgQa/D6mkG2Hhnw9KhhcdHAB36WdYDpYu1CIVNi01 k9QmqsKD4dGfYcC8ur+Ra61qmm/Vhofc2jQ1UT8sedqgOUrg9fGSvITSWyWGk+BBJI sV1s3ZzMq7COHLlLELCKcUR3s/yQBjFJ0b3gltuY= Received: from delight.greenbytes.local (unknown [192.168.1.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail.greenbytes.de (Postfix) with ESMTPSA id 0927615A14FE for ; Mon, 3 Apr 2017 13:25:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=greenbytes.de; s=mail; t=1491218730; bh=QuPquzsMPdIyxnh1FgJh0EC4tc5TxA5/42X7iBm+wsk=; h=From:Subject:Date:References:To:In-Reply-To:From; b=ltYty3+d5uZ32R7FkCf4+bXHT2VBnGJos3lNjNNa/3P/Shn1JLv3TqDz5N00BdLgW ctjX8qJhp/AiEiYecf6TB2PMh+NTyEgMaKc+8rOCVLKww+RALDHfLL9OYglZOaUjOt pr5l2dnDZlIydd+r4qpDZUneB0Bxjo4xGLPFSlgg= From: Stefan Eissing Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Upgrade header Date: Mon, 3 Apr 2017 13:25:29 +0200 References: <928d0b55-b18b-480b-820a-cadcfe800b22@hoentjen.eu> To: dev@httpd.apache.org In-Reply-To: <928d0b55-b18b-480b-820a-cadcfe800b22@hoentjen.eu> Message-Id: <84D9EBA1-42D6-4903-AEB8-E47BFC1C5398@greenbytes.de> X-Mailer: Apple Mail (2.3273) archived-at: Mon, 03 Apr 2017 11:25:38 -0000 https://tools.ietf.org/html/rfc7230#section-6.7: "A server MAY send an Upgrade header field in any other response to advertise that it implements support for upgrading to the listed protocols, in order of descending preference, when appropriate for a future request." Yes, it is intentional to advertise this to clients on the first request of a connection. To disable this, you can "unset" such a header via mod_headers. Hope this helps. -Stefan > Am 03.04.2017 um 13:10 schrieb Sander Hoentjen : > > Hi Stefan (and others), > > Right now when I enable h2 and/or h2c Apache will respond with headers > "Upgrade: h2,h2c" and Connection: Upgrade > As I understand it this is the wrong way around. Only the client should > send the Upgrade headers, and only then should the server respond with a > 101 with the Upgrade header only specifying the proto that is being > switched to. > Is this a bug, or does Apache respond intentionally with the Upgrade > header? If intentional, then what is the reason? > > Regards, > Sander