Re: Ambiguity when handling DATA frames on closed streams

The reason it's not stream closed in section 6.1 is the stream may be in
the idle state when you receive the DATA frame.


On Mon, Dec 2, 2013 at 10:57 AM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 29 November 2013 08:48, Alan Shreve <alan@inconshreveable.com> wrote:
> > However, Section 6.1 "DATA":
> >
> > "If a DATA frame is received whose stream is not in "open" or "half
> closed
> > (local)" state, the recipient MUST respond with a connection error
> (Section
> > 5.4.1) of type PROTOCOL_ERROR ."
>
> Good catch.  I think that this is the part that is wrong.  Until and
> unless I hear screams, I'll fix 6.1 to match the rest of the document.
>
>
> https://github.com/http2/http2-spec/commit/b6345121badab90d93c336c11c1278f948d7390a
>
>

Received on Monday, 2 December 2013 19:12:51 UTC