W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2014

Re: GOAWAY and proxies (#458)

From: Daniel Sommermann <dcsommer@fb.com>
Date: Fri, 2 May 2014 16:44:01 -0700
Message-ID: <53642DC1.1070805@fb.com>
To: "William Chan (ι™ˆζ™Ίζ˜Œ)" <willchan@chromium.org>, Roberto Peon <grmocg@gmail.com>
CC: Martin Thomson <martin.thomson@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
I updated the language on the pull request (mostly copying Martin's 
suggestions): https://github.com/http2/http2-spec/pull/475/files

It adds this text to section 6.8:

           A client that is unable to retry requests loses all requests 
that are in flight when the
           server closes the connection. This is especially true for 
intermediaries that might
           not be serving clients using HTTP/2. A server that is 
attempting to gracefully shut down
           a connection SHOULD send an initial GOAWAY frame with the 
last stream identifier set to
           2<x:sup>31</x:sup>-1 and a <x:ref>NO_ERROR</x:ref> code. This 
signals to the client that
           a shutdown is imminent and that no further requests can be 
initiated. After waiting at
           least one round trip time, the server can send another GOAWAY 
frame with an updated last
           stream identifier. This ensures that a connection can be 
cleanly shut down without losing
           requests.
Received on Friday, 2 May 2014 23:44:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:30 UTC