W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2014

PUSH_PROMISE associated stream

From: Daniel Sommermann <dcsommer@fb.com>
Date: Mon, 10 Mar 2014 14:46:13 -0700
Message-ID: <531E32A5.2050406@fb.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
 From 6.6 PUSH_PROMISE:

PUSH_PROMISE frames MUST be associated with an existing, peer-initiated 
stream. If the stream identifier field specifies the value 0x0, a 
recipient MUST respond with a connection error (Section 5.4.1 
<http://http2.github.io/http2-spec/index.html#ConnectionErrorHandler>) 
of type PROTOCOL_ERROR 
<http://http2.github.io/http2-spec/index.html#PROTOCOL_ERROR>.

Is this a vestigial carry-over from SPDY? I don't see an 
"Associated-To-Stream-ID" field in PUSH_PROMISE. At first glance, it 
looks like HTTP/2 does away with requirement that a pushed resource be 
associated with a client-initiated stream.
Received on Monday, 10 March 2014 21:46:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:24 UTC