- From: Matthew Cox <macox@microsoft.com>
- Date: Wed, 8 Oct 2014 16:25:15 +0000
- To: Mark Nottingham <mnot@mnot.net>, Martin Thomson <martin.thomson@gmail.com>
- CC: Greg Wilkins <gregw@intalio.com>, Osama Mazahir <OSAMAM@microsoft.com>, Jeff Pinner <jpinner@twitter.com>, Michaela LaVan <mlavan@google.com>, "Mike Bishop" <Michael.Bishop@microsoft.com>, HTTP Working Group <ietf-http-wg@w3.org>
This is still a -1 from our side. Does RST_STREAM with NO_ERROR transition state to "closed", or is this a new state? Obviously all data up to the other side's window must be allowed (because it may already be in flight), but will the receiver keep opening window after sending this new kind of RST_STREAM? The way it reads right now, it almost sounds like RST_STREAM (NO_ERROR) is advisory and doesn't transition the stream to the terminal state. If this is the case then there is a simple workaround for us; we just ignore RST_STREAM (NO_ERROR). Matthew -----Original Message----- From: Mark Nottingham [mailto:mnot@mnot.net] Sent: Tuesday, October 07, 2014 3:51 PM To: Martin Thomson Cc: Greg Wilkins; Osama Mazahir; Jeff Pinner; Matthew Cox; Michaela LaVan; Mike Bishop; HTTP Working Group Subject: Re: RST_STREAM(OK) after an HTTP response Thanks. I think we're close to consensus on this -- anyone have further questions / pushback? Cheers, On 8 Oct 2014, at 9:02 am, Martin Thomson <martin.thomson@gmail.com> wrote: > On 6 October 2014 23:15, Mark Nottingham <mnot@mnot.net> wrote: >> Martin, can you please prepare a pull request here? > > https://github.com/http2/http2-spec/pull/624 -- Mark Nottingham https://www.mnot.net/
Received on Wednesday, 8 October 2014 16:25:45 UTC