- From: Mike Bishop <Michael.Bishop@microsoft.com>
- Date: Thu, 7 Jan 2016 19:01:40 +0000
- To: Stefan Eissing <stefan.eissing@greenbytes.de>, HTTP Working Group <ietf-http-wg@w3.org>
Yes, it SHOULD send the GOAWAY, which implies that it can also reasonably close the connection without sending it. It's not a MUST, because sending it is always optional and sometimes serves no real purpose. You've identified one of the latter. -----Original Message----- From: Stefan Eissing [mailto:stefan.eissing@greenbytes.de] Sent: Thursday, January 7, 2016 10:39 AM To: HTTP Working Group <ietf-http-wg@w3.org> Subject: GOAWAY after GOAWAY Question arising during implementation: A hypothetical http server receives a GOAWAY from a client with no streams open. Should it attempt to send a GOAWAY back or can it safely close the connection? rfc 7540. 6.8 seems to say that endpoints SHOULD always send a GOAWAY. But it seems not useful in such a case. Probably I am overlooking something? -Stefan
Received on Thursday, 7 January 2016 19:02:11 UTC