W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2015

Streams after receiving GOAWAY

From: Glen Knowles <gknowles@ieee.org>
Date: Sun, 15 Nov 2015 02:24:15 -0800
Message-ID: <CAJCH0yBs5LxvYmgvbLHX7NgSptfBUF4TB7tw_OeuyFpTiiLbUg@mail.gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
I'm about to deliberately violate the letter of a MUST NOT because I
believe it's overly strict.

"Receivers of a GOAWAY frame MUST NOT open additional streams on the

When my server wants to close a connection it sends a GOAWAY with last
stream id set to a value somewhat higher than anything it has received. It
then keeps the connection until the reported last id is reached or enough
time goes by.

When the client gets a GOAWAY it will immediately start establishing a new
connection, continue issuing new requests up to the reported last id, and
close the old connection when it either has a new connection or has used
all the reported streams.

The goal is to avoid suspending requests in a high volume server to server
environment while waiting for new connections. I don't see how it conflicts
with any conforming implementation, am I missing something?

Received on Sunday, 15 November 2015 10:24:44 UTC

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