Re: [quicwg/base-drafts] Truncated http stream error handling is aggressive (#2718)

Martin Thomson <> Fri, 17 May 2019 10:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B782E120228 for <>; Fri, 17 May 2019 03:26:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.464
X-Spam-Status: No, score=-6.464 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 1moCJ-WxucaL for <>; Fri, 17 May 2019 03:26:15 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 06C471201ED for <>; Fri, 17 May 2019 03:26:15 -0700 (PDT)
Date: Fri, 17 May 2019 03:26:14 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558088774; bh=EdTsleeadLtSjNOm5HaCTy4B66T4E+QFJEKi/nI0Nvs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nOI3St6OLhmcpon9q0+HPo+Ay7potxQTH90j+PW7424TYYZl0yHZYPcZ4Y09DhiZu eLvgq9EPDVbqvOiWeVQPyU0hKTmxsDMXlfzQ11H8CdzJVKWTj6zcG5HmzKbOSEUgSy QNnd6EibSM8D/hFfARiU5EedmkUocDZ48zfMsz/k=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2718/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Truncated http stream error handling is aggressive (#2718)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cde8c46ca8d_57293ff4ebacd96834252a"; 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
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: Fri, 17 May 2019 10:26:17 -0000

If you create a stream that is invalid, then it is perfectly reasonable to kill the connection.  If you make a bad prediction that results in having to abandon a stream, then RESET_STREAM is the tool you use.  You don't close the stream as though it was OK.

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