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

Re: INVALID_STREAM and STREAM_ALREADY_CLOSED

From: Roberto Peon <grmocg@gmail.com>
Date: Tue, 26 Mar 2013 12:34:35 -0700
Message-ID: <CAP+FsNcy1KA0qs=knJzfyfcwjUbWAsWGB9zL5PjAFbrp+V5OwA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
imho: Seems reasonable for now.
I expect that we'll expand the error codes as more implementors find error
conditions that they want to be able to debug from a client debug
information, at which point we can re-add any of this.

-=R


On Tue, Mar 26, 2013 at 11:23 AM, Martin Thomson
<martin.thomson@gmail.com>wrote:

> Another error code question.
>
> INVALID_STREAM indicates that a frame arrived for an "inactive" stream.
>
> STREAM_ALREADY_CLOSED indicates that a frame arrived for a (half-)closed
> stream.
>
> Both are unexpected frames.  My first inclination was to suggest
> (again) that a single error code was appropriate.
>
> However, if I read between the lines, INVALID_STREAM is as a result of
> getting a frame prior to the first 'official' frame in the stream
> (i.e., SYN_STREAM).  But the general design doesn't require that a
> stream starts with any particular frame.
>
> So I conclude that it only makes sense to have STREAM_ALREADY_CLOSED.
>
>
Received on Tuesday, 26 March 2013 19:35:07 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 19:35:09 GMT