Re: [quicwg/base-drafts] Servers should always send CANCEL_PUSH (#3700)

ianswett <> Wed, 27 May 2020 12:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7C9003A0DDC for <>; Wed, 27 May 2020 05:07:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Status: No, score=-1.555 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 zGITfiaEmIJi for <>; Wed, 27 May 2020 05:07:39 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3ADA53A0DDB for <>; Wed, 27 May 2020 05:07:39 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 7CD832C21F1 for <>; Wed, 27 May 2020 05:07:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1590581258; bh=h6EFZ8jhvCESP2ASMN6eURkBuLjJQl2EmMfGYER+aYo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=CEoMMfT1Sq3bTqoQGwe5Dka/x5Hb383uX5YzbuD3ST4XUkf4DyVwXKAHNB0sDc7j0 yw6hagbpROfPDNizPOQK6AvfG4wLw9nT8Kzfq5yFWPKCzeub1d1VQbjQEuiE/4/SJv kF3GXaEqKfTbUfMkqbddUSOEzzv7B8LTjjP9znCg=
Date: Wed, 27 May 2020 05:07:38 -0700
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3700/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Servers should always send CANCEL_PUSH (#3700)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ece580a6ae51_31313fa52d2cd9601138a5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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, 27 May 2020 12:07:41 -0000

@ianswett commented on this pull request.

>  When a server sends CANCEL_PUSH, it is indicating that it will not be fulfilling
-a promise and has not created a push stream.  The client should not expect the
-corresponding promise to be fulfilled.
+a promise.  The client cannot expect the corresponding promise to be fulfilled.
+A server SHOULD send a CANCEL_PUSH even if it has opened the corresponding

That matches what would occur in transport, so it does seem like the right call.

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