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

Mike Bishop <> Fri, 17 May 2019 18:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B34B712015D for <>; Fri, 17 May 2019 11:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.464
X-Spam-Status: No, score=-1.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, 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 LPBYO0jgcKcA for <>; Fri, 17 May 2019 11:00:20 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DD9EE12013D for <>; Fri, 17 May 2019 11:00:19 -0700 (PDT)
Date: Fri, 17 May 2019 11:00:18 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558116018; bh=3PxnHt2Ue2eE8faJbU7SYiIWdJxAcI+ZKqzqzvZ3f8U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=osXt1x8E+90fDCPMD/v2S1LPCq0kpSrHxj0xTebi/Pc90twmspHrRIrPOFAN2GBuB xHkg3tS8ZpPGINibY/kvl314EXfk2y36KRjrj+UEb4E/6lwMGof75iT0moL/Qy2OkL 89KClttIVbF0766kQaDKocNu2WhsvDwGDmTfpFLY=
From: Mike Bishop <>
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_5cdef6b2a733a_1cb03fc27b2cd96859299"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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 18:00:22 -0000

I actually encountered this bug in the past, where the server decided to truncate a response but didn't indicate that there was an abort.  Then the truncated response was cached and served to future clients.

If you're not going to finish the response, RESET the stream so everyone knows it.

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