[quicwg/base-drafts] Is absence of both :authority and Host an error? (#3408)

Mike Bishop <notifications@github.com> Tue, 04 February 2020 10:58 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1B2C120088 for <quic-issues@ietfa.amsl.com>; Tue, 4 Feb 2020 02:58:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level:
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
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 TZnUa_KIVQWC for <quic-issues@ietfa.amsl.com>; Tue, 4 Feb 2020 02:58:36 -0800 (PST)
Received: from out-19.smtp.github.com (out-19.smtp.github.com [192.30.252.202]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52DE2120046 for <quic-issues@ietf.org>; Tue, 4 Feb 2020 02:58:36 -0800 (PST)
Date: Tue, 04 Feb 2020 02:58:35 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1580813915; bh=WQgPxVcQYsP//FEpJS5Xu0ECBV7ll49sH5M9bxRobZU=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=mraZQByz+u8l526CyEJvaYu19tg1XxcFnS6YLBIxlNJP3GhRrYZaCxv5NPf+yEKJ9 0dS0mKv2NbitKj2pqSsXLGvqlvyezGa6aq3ZP4sa5QgwqXitTkKlSZ81u0Onc+D9VO ugt8ZS4WK7gQa0vE9p04S5zGJL43YqSN5UHTkUI0=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6AW47SDQ5VA3IKDE54I2ANXEVBNHHCCW3TFU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3408@github.com>
Subject: [quicwg/base-drafts] Is absence of both :authority and Host an error? (#3408)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e394e5b39789_63ef3fd4b28cd964148629"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/IYALQvW-0eVMbD3MuKTNjjVmrHA>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2020 10:58:38 -0000

>From an interop discussion with @martinduke and @kazuho.

HTTP/1.1 [requires](https://httpwg.org/http-core/draft-ietf-httpbis-semantics-latest.html#header.host) the presence of a Host header:
> A client MUST send a Host header field in all HTTP/1.1 request messages. If the target URI includes an authority component, then a client MUST send a field value for Host that is identical to that authority component, excluding any userinfo subcomponent and its "@" delimiter (Section 2.5.1). If the authority component is missing or undefined for the target URI, then a client MUST send a Host header field with an empty field value.
If no Host header is present, the section on [Effective Request URI](https://httpwg.org/http-core/draft-ietf-httpbis-messaging-latest.html#h1.effective.request.uri) describes how you determine what host is being asked for, ending with "heuristics" if it's an HTTP/1.0 request.

HTTP/2 says that you generate an `:authority` pseudo-header if sending direct-to-H2 and carry through the Host header if you're relaying HTTP/1.1.  There is no discussion about what to do with an HTTP/1.0 (or 0.9) request being relayed over HTTP/2, which wouldn't have a Host header; you're neither required to generate or send one, even an empty one, nor are you given guidance about how to figure it out.

HTTP/3 carries forward the H2 language (currently by reference, and explicitly after #3407).  Do we want to have some guidance here?  Or does this issue instead belong in https://httpwg.org/http-core/ to move some of the existing guidance to be HTTP version-independent?

(@royfielding)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3408