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

Re: Connection fatal HTTP/2 stream errors

From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 18 Jun 2014 12:12:59 -0700
Message-ID: <CABkgnnWKFyARoC6i5XUKM-bZdNAoXQZBTbM-gQFe31WpYLQ7-g@mail.gmail.com>
To: Greg Wilkins <gregw@intalio.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
On 18 June 2014 02:32, Greg Wilkins <gregw@intalio.com> wrote:
> we are currently leaning towards treating all stream errors as fatal to the
> connection.

This fits with our current error handling philosophy.

The general sense here has been that failing hard is preferred at this
stage.  Postel's principle leads to the sorts of sloppiness that
HTTP/1.1 suffers from in excess, and the more we can do to expose
errors now, the less we will have to deal with corner cases later.

All of the errors you cite can, and probably should, be fatal to the
extent that is reasonable.  Obviously, you can't catch everything, and
things like bad paths might simply be forwarded on from HTTP/1.1,
where that sort of crap appears all the time.

On the other hand, if you are operating a server, you are free to be
more strict.  Don't abuse it, but you can enforce a fairly arbitrary
dress code.
Received on Wednesday, 18 June 2014 19:13:26 UTC

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