Re: [quicwg/base-drafts] Rationalise Server-Push-specific rejection error codes (#2812)

Kazuho Oku <> Wed, 19 June 2019 12:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A1E33120228 for <>; Wed, 19 Jun 2019 05:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.463
X-Spam-Status: No, score=-6.463 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_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 4NKgHy-P1PDG for <>; Wed, 19 Jun 2019 05:37:34 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1B87912015A for <>; Wed, 19 Jun 2019 05:37:34 -0700 (PDT)
Date: Wed, 19 Jun 2019 05:37:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1560947853; bh=i8nqJmVW+yWM5buf6eKLgGSrHtxxJgcStS0ZE5QHw2c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pr0j3fwNMGvPoK519QaUSnKBh4bcqmPL71JSWJ0ZZWb+iEByEd3ndJUuwNoOHSdta 8pMbJDpFq2CgsJfo31i2wW3P8Neqbcj/sAKQEigNd1d4YpvGQHStHczHctFNA4QELr RAhNihfDI33MENUJIE8Fljd4CR73/a1D/AQL3sq8=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2812/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Rationalise Server-Push-specific rejection error codes (#2812)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d0a2c8cf2947_3c533fed58acd96c812896"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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, 19 Jun 2019 12:37:36 -0000

I agree that we can remove HTTP_PUSH_ALREADY_IN_CACHE.

In addition, I think we might also want to remove CANCEL_PUSH in favor of using REQUEST_CANCELLED. IIUC, the semantics of CANCEL_PUSH can be (or can be) exactly the same as REQUEST_CANCELLED after the client has sent the entire request.

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