Re: [quicwg/base-drafts] Clarify that tunnels can send malformed HTTP message, and it is not a connection-level error (#3303)

Martin Thomson <notifications@github.com> Wed, 18 December 2019 04:21 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 12F72120866 for <quic-issues@ietfa.amsl.com>; Tue, 17 Dec 2019 20:21:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-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 5uq2NILCiGxF for <quic-issues@ietfa.amsl.com>; Tue, 17 Dec 2019 20:21:10 -0800 (PST)
Received: from out-20.smtp.github.com (out-20.smtp.github.com [192.30.252.203]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA7FC120801 for <quic-issues@ietf.org>; Tue, 17 Dec 2019 20:21:09 -0800 (PST)
Received: from github-lowworker-f144ac1.va3-iad.github.net (github-lowworker-f144ac1.va3-iad.github.net [10.48.16.59]) by smtp.github.com (Postfix) with ESMTP id 36B008C06CD for <quic-issues@ietf.org>; Tue, 17 Dec 2019 20:21:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1576642869; bh=fp55kSi8NfRNnUbxxYUqFZ3Fug0Xx+oOC4zPP4mN/Hw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=V5HOMGiw86vn94OiZSrB/uM99v2jDslxuBfjpf3qx8pEEDlcAhM0kSdGPgdSUUVfK V7Dj+MX591QxQHI6WAGz9+epIbmU4BKmBEONWlA5pVV6ei5qMIbDEwgKz7Fi6plrJp lQ7knzRGQ0Ou/+6EuvqJ2iXvH4mq8rBMkNFpPmxY=
Date: Tue, 17 Dec 2019 20:21:09 -0800
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7RU2NQFE72O4RNQYF4A3N3LEVBNHHCAHIHBM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3303/review/333722379@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3303@github.com>
References: <quicwg/base-drafts/pull/3303@github.com>
Subject: Re: [quicwg/base-drafts] Clarify that tunnels can send malformed HTTP message, and it is not a connection-level error (#3303)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5df9a935273b5_7cf3ffb8a8cd960160a1"; 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/GDRWzfb9UVHuWzu_Yzd2eM6tByU>
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: Wed, 18 Dec 2019 04:21:11 -0000

martinthomson commented on this pull request.



> @@ -536,6 +536,11 @@ not acting as a tunnel) MUST NOT forward a malformed request or response.
 Malformed requests or responses that are detected MUST be treated as a stream
 error ({{errors}}) of type H3_GENERAL_PROTOCOL_ERROR.
 
+A tunnel that dispatches HTTP messages to different endpoints might forward a

I think that this is a "cannot" rather than a "MUST NOT".  What that intermediary does is up to them.  It might be inadvisable to have errors from one source affect all of the sources that share the same connection, but that's their call.

-- 
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/pull/3303#discussion_r359146165