W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2013

RST_STREAM and FINAL flag

From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 25 Apr 2013 12:12:33 -0700
Message-ID: <CABkgnnWWAME+moOkPxMHzO7za0t8_TvHeKwWAC-z+GEk2P_+7Q@mail.gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
James raised this:

https://github.com/http2/http2-spec/issues/77

"... what is not explicitly stated anywhere in the draft is that the
FINAL flag for the RST_STREAM frame MUST be set. Likewise with
GOAWAY..."

I don't think that it matters what the FINAL flag says for RST_STREAM
- processing the frame closes the stream in totality, so whether the
stream gets half-closed in the process is largely irrelevant.  Same
for GOAWAY.

Also, "what happens if an endpoint sends a RST_STREAM with stream
identifier #0 ? "

My take: this is very bad.  Don't do that, but if you do see it, then
it's a PROTOCOL_ERROR.
Received on Thursday, 25 April 2013 19:13:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:12 UTC