Re: [quicwg/base-drafts] Remove HTTP_PUSH_ALREADY_IN_CACHE error (#2813)

Lucas Pardue <> Thu, 20 June 2019 00:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 661FB120134 for <>; Wed, 19 Jun 2019 17:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.008
X-Spam-Status: No, score=-8.008 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 nbY-rhz-T692 for <>; Wed, 19 Jun 2019 17:57:22 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2DE2C12012A for <>; Wed, 19 Jun 2019 17:57:22 -0700 (PDT)
Date: Wed, 19 Jun 2019 17:57:20 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1560992240; bh=2l6cukD5btXm45QH9lyB6FYojME/vF9+Hb+OZAtfbhI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=D+/JEsSx5kVq3eia/VJENk5VsQyYSCCnVI/5Pju5NR/Id7BZKR5kvnQxIQvaAmwvs Yfu/XDCb8KD+adVghkb5mlmsv8PBQ0BWWzxUr8LUmQZzSzWs3RFy6Q9gjac580Mw+w u9F7WAJx0nf2cMLvXFsLaoav/rE2OJxTYSghUAlE=
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2813/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Remove HTTP_PUSH_ALREADY_IN_CACHE error (#2813)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d0ad9f0a7fdc_78c23fce93ccd96c225061"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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: Thu, 20 Jun 2019 00:57:25 -0000

LPardue commented on this pull request.

> @@ -785,10 +785,9 @@ amount of data a server may commit to the pushed stream.
 If a promised server push is not needed by the client, the client SHOULD send a
 CANCEL_PUSH frame. If the push stream is already open or opens after sending the
-CANCEL_PUSH frame, a QUIC STOP_SENDING frame with an appropriate error code can

It is an error, thanks for picking it up. I would convert this to

"a QUIC STOP_SENDING frame with an error code of HTTP_REQUEST_CANCELLED can be used."

Alternatively, elsewhere we talk about "triggering QUIC STOP_SENDING" which is under review as part of @MikeBishop #2805 

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