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


From: David Morris <dwm@xpasc.com>
Date: Wed, 19 Jun 2013 07:41:37 -0700 (PDT)
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-ID: <alpine.LRH.2.01.1306190738140.31315@egate.xpasc.com>

On Wed, 19 Jun 2013, Patrick McManus wrote:

> On Wed, Jun 19, 2013 at 2:00 AM, James M Snell <jasnell@gmail.com> wrote:
> > https://github.com/http2/http2-spec/issues/140
> >
> > Currently, we have the FRAME_TOO_LARGE error code...
> >
> > suggestion is to remove FRAME_TOO_LARGE entirely and just use
> yes, let's do that! FRAME_TOO_LARGE's purpose was when the frame exceeded
> client capacity - not for malformed packets. With the new smaller frame
> sizes that bit of complexity can and should just go away.

I think more information on error conditions is almost always better. The
recipient should always beable to fold multiple codes into one if they

In any case, I haven't seen a discussion on the list, but at the interim
meeting, the maximum was pushed up to HTTP while allowing the framing
layer to retain the 64k limit implied by the field size. That seems to
me to mean that the http layer could still need to send the TOO_LARGE
Received on Wednesday, 19 June 2013 14:42:06 UTC

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