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

Kazuho Oku <> Wed, 18 December 2019 01:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C9462120096 for <>; Tue, 17 Dec 2019 17:50:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jGi1fD3lXb_i for <>; Tue, 17 Dec 2019 17:50:36 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 63185120073 for <>; Tue, 17 Dec 2019 17:50:36 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 59F36C60358 for <>; Tue, 17 Dec 2019 17:50:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1576633835; bh=6TC+x//EWFErh1UJ/emSwDoWCRm7uUyrgESd7akCVNg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vTHnNHaUaCne0dtK8xsgUTm9wCv9NrL7QM/xXnUqaJf1r/lLFNLNSK+sw+AKwVV3c c13t2h9nFACY4NcPlr1hNQp08/gbxlEqQK5Kj8pqEWdFdG1g9Ef6V8nIjllBJUzLbI TP8MM+/QACC4AXD6pjGwJqSfBw9jNV69jqhz7yoM=
Date: Tue, 17 Dec 2019 17:50:35 -0800
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3303/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
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_5df985eb4b130_3b553fe9608cd960951b"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 18 Dec 2019 01:50:38 -0000

Seeing distaste for endorsing an intermediary to send a corrupt frame intentionally, I have changed the text to be a clarification of what we already have.

The paragraph that precedes the new paragraph being proposed in this PR states that, quote: "Intermediaries that process HTTP requests or responses (i.e., any intermediary
not acting as a tunnel) MUST NOT forward a malformed request or response."

The flip-side is that tunnels are allowed to send malformed HTTP messages. As a tunnel might be coalescing messages from multiple endpoints onto a single connection, receipt of a malformed HTTP message cannot be considered as a connection-level issue.

This PR clarifies that.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: