Re: REFUSED_STREAM => RETRY_STREAM (editorial) was: RE: hpack table size 0 from Martin Thomson on 2014-08-01 (ietf-http-wg@w3.org from July to September 2014)

From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 1 Aug 2014 09:25:14 -0700
To: "K.Morgan@iaea.org" <K.Morgan@iaea.org>
Cc: Mike Bishop <Michael.Bishop@microsoft.com>, HTTP Working Group <ietf-http-wg@w3.org>, Mark Nottingham <mnot@mnot.net>
Message-ID: <CABkgnnW6WjDhKV6v6QsT0a0zkZgvZhsoUMv0MFUTVu8tWxh3fg@mail.gmail.com>

On 1 August 2014 02:44,  <K.Morgan@iaea.org> wrote:
> The definition of REFUSED_STREAM is somewhat contradictory with the
> definition of the word refused. The word refused is defined as: indicate or
> show that one is *not willing* to do something [1]. The definition of
> REFUSED_STREAM in Section 7 references section 8.1.4 which says that a
> REFUSED_STREAM is safe to retry. In other words the server is actually
> *willing* to process the stream, but *currently unable* (e.g. because the
> client overran settings and so the client needs to retry the stream with the
> new settings).

I'm not sure that I agree with this assessment.  Does anyone else?

Received on Friday, 1 August 2014 16:25:43 UTC