W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013


From: Roberto Peon <grmocg@gmail.com>
Date: Tue, 26 Mar 2013 13:28:12 -0700
Message-ID: <CAP+FsNefrP7Sb_4THAPDLUGV0zFOZNRFtfXhAh=RUisvv=bd_A@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: William Chan (陈智昌) <willchan@chromium.org>, HTTP Working Group <ietf-http-wg@w3.org>
You (rather, a browser) can automatically send the request again in the
case where a non-idempotent method such as POST was used.
With cancel, the browser would have to ask the client to confirm before
doing so.

On Tue, Mar 26, 2013 at 1:16 PM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 26 March 2013 12:42, William Chan (陈智昌) <willchan@chromium.org> wrote:
> > REFUSED_STREAM says it was refused before any processing happened.
> The temporal distinction ("before any processing happened") isn't a
> useful one.  "Do not want" and "do not want any more" are so finely
> graded in distinction as to be meaningless.
> More importantly, given that a stream can contain frames that mutate
> session state, ALL frames need to be processed to some extent.  If
> this is to mean that it never surfaced above the framing layer, I
> don't believe that information is actionable.
> > The
> > client knows that it's safe to retry the SYN_STREAM later on [...]
> Presumably not for the same stream ;)
> Bottom line: what do I do differently in response to a refused stream
> as opposed to a cancelled one?
Received on Tuesday, 26 March 2013 20:28:39 UTC

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