Re: [quicwg/base-drafts] Clarify use of HTTP request with http scheme over HTTP/3 (#2439)
Martin Thomson <notifications@github.com> Mon, 11 February 2019 01:00 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 DE845130E5E for <quic-issues@ietfa.amsl.com>; Sun, 10 Feb 2019 17:00:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Level:
X-Spam-Status: No, score=-6.596 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_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 cKXGguIJMHss for <quic-issues@ietfa.amsl.com>; Sun, 10 Feb 2019 17:00:26 -0800 (PST)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09A99130E57 for <quic-issues@ietf.org>; Sun, 10 Feb 2019 17:00:25 -0800 (PST)
Date: Sun, 10 Feb 2019 17:00:24 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1549846824; bh=VcIrmhx2diPjqh33eJtZmbxegQgXXQWrHShy6KxSdv8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=u5qJQ5TzhPuXKb6dbGRa3Q9mnkPNAe2+Zov48mNmYtEbNKmngAtmU58ZNwaTkC+fg DsRFavj5OhQZ4ny8ENkXJmq2jUBUOPFKDgiWgEqwLGvbsvVxJ3fG8q7P0ZwSeMrfpw R7D+DfKO854DI73ldTC15XZ/IW3JUApCM6+y4FGI=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1195f477be8783fdd66c5d48852da4ebc4cbf89b92cf0000000118788b2892a169ce1854ec6b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2439/462198512@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2439@github.com>
References: <quicwg/base-drafts/issues/2439@github.com>
Subject: Re: [quicwg/base-drafts] Clarify use of HTTP request with http scheme over HTTP/3 (#2439)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c60c928c6faf_38503fb080ed45c041104a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/CSphWNKD9fPQSUccVvfdedCsX4c>
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: Mon, 11 Feb 2019 01:00:28 -0000
I'd rather duplicate this to #253 and rely on [RFC 8164](https://tools.ietf.org/html/rfc8164) for this. We were not very careful in that document to avoid mention of the specific HTTP version, but the technique is perfectly portable between versions. We only really intended to put HTTP/1.x off limits. -- 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/2439#issuecomment-462198512
- [quicwg/base-drafts] Clarify use of HTTP request … Magnus Westerlund
- Re: [quicwg/base-drafts] Clarify use of HTTP requ… Lucas Pardue
- Re: [quicwg/base-drafts] Clarify use of HTTP requ… Mike Bishop
- Re: [quicwg/base-drafts] Clarify use of HTTP requ… Martin Thomson
- Re: [quicwg/base-drafts] Clarify use of HTTP requ… Mike Bishop
- Re: [quicwg/base-drafts] Clarify use of HTTP requ… Martin Thomson
- Re: [quicwg/base-drafts] Clarify use of HTTP requ… Mike Bishop
- Re: [quicwg/base-drafts] Clarify use of HTTP requ… Mike Bishop