Re: [quicwg/base-drafts] Forwarding upstream error mid-body to downstream (#3300)

Jana Iyengar <> Mon, 16 December 2019 20:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B157C120912 for <>; Mon, 16 Dec 2019 12:19:24 -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 sP0AscHja71o for <>; Mon, 16 Dec 2019 12:19:23 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id F3BC312090F for <>; Mon, 16 Dec 2019 12:19:22 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 4658066084B for <>; Mon, 16 Dec 2019 12:19:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1576527562; bh=tHlDVg5ExvS73tPHsBbZ+LfAEDmSLE1skL6fYAARZ/w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=YB11+9ymHQQV2jAkcERx57uL1df134VLhPO3Kww5Ifcq1oen2UnjVzHmkbnIdKmO1 XqMhae3MLTJSMJzvTPlROq8XtbLBmPhYAOg0CwCQ/JKaQolAKvee48zWKG4EgfeA0M oPUQXxWD1vRfaVXVvhEqkj0yf9bqt61sKUw8OsXk=
Date: Mon, 16 Dec 2019 12:19:22 -0800
From: Jana Iyengar <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3300/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Forwarding upstream error mid-body to downstream (#3300)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5df7e6ca37e09_4f053fe2de2cd96c123433"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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: Mon, 16 Dec 2019 20:19:25 -0000

@ianswett's point is right: there's no guarantee what the proxy has read out of a connection that has received a TCP RST. Additionally, there's no guarantee that the H1 sender's pending data has been sent out of its TCP buffers yet either.

@kazuho: Do you think think this is somehow different?

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