Re: [quicwg/base-drafts] Why are there two ways of associating push with requests? (#3275)

Kazuho Oku <> Wed, 27 November 2019 12:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A892D120894 for <>; Wed, 27 Nov 2019 04:04:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 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, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 nGWNWYJgJLfv for <>; Wed, 27 Nov 2019 04:04:28 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 644F912088F for <>; Wed, 27 Nov 2019 04:04:28 -0800 (PST)
Date: Wed, 27 Nov 2019 04:04:27 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1574856267; bh=jKXFGkjQmW97e7LwUxDP1DmJLqq3BuNgQ70swa/BGzU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Ij4u+kmXflbMQo3Twv4QbFNOTHWPisCS7i78irayCV9EHjhVK3BubcIHw5IRbhaLi FbhM0cMx+fbivVltLOCi3xRq4td7jWSW9v/H4DQU5ypItjQ2Q++gOt6WCh5sRzuCtv 5Lmz7P1yj16iHcSIZiWc5Jx0qU8aLZFgCKbOhpis=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3275/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Why are there two ways of associating push with requests? (#3275)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dde664b99278_272a3ff89a0cd9602064a8"; 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, 27 Nov 2019 12:04:30 -0000

@LPardue Good point. It can be a new frame, or I think it can also be a HEADERS frame.

In case of the latter, the first HEADERS frame would be the request, and the second HEADERS frame would be the response headers. This can be guaranteed since a push request is never accompanied by a request body.

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