[quicwg/base-drafts] Description of "HTTP Message Exchanges" should explicitly PUSH

[quicwg/base-drafts] Description of "HTTP Message Exchanges" should explicitly PUSH_PROMISE headers. (#741)

krasic <notifications@github.com> Thu, 17 August 2017 18:49 UTC

Date: Thu, 17 Aug 2017 18:48:58 +0000
From: krasic <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab39bfbc2e0ffa61527ffa4b4623ac35b5e863a48992cf0000000115ada71992a169ce0ef685fb@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/741@github.com>
Subject: [quicwg/base-drafts] Description of "HTTP Message Exchanges" should explicitly PUSH_PROMISE headers. (#741)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5995e519ef285_44963fafdec21c308972f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/ZFHrTzI0rnPElcZqEpmqjRv0pJY>

[HTTP Message Exchanges](https://tools.ietf.org/id/draft-ietf-quic-http-05.html#rfc.section.4.2) should have text to describe PUSH_PROMISES.  Notably the case of promises interleaved with body data frames *after* the stream's own response headers, since this was a prime motivation for reverting from the previous draft's scheme to the present one.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/741

[quicwg/base-drafts] Description of "HTTP Message… krasic
Re: [quicwg/base-drafts] Description of "HTTP Mes… Mike Bishop
Re: [quicwg/base-drafts] Description of "HTTP Mes… Mike Bishop