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

Error code for PING frame with wrong size - https://github.com/http2/http2-spec/issues/246

From: (wrong string) 陈智昌 <willchan@chromium.org>
Date: Mon, 16 Sep 2013 18:17:37 -0700
Message-ID: <CAA4WUYjKwdANzYU8T4md6pGR5FODuUF3Tghryh9czvWrjKVigg@mail.gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
Moving over from github.

Gabor:
==========
Currently, there's two contradicting MUSTs for this.

Section 4.2::

Certain frame types, such as PING (see Section 6.7), impose
additional limits on the amount of payload data allowed.  Likewise,
additional size limits can be set by specific application uses (see
Section 9).

If a frame size exceeds any defined limit, or is too small to contain
mandatory frame data, the endpoint MUST send a FRAME_TOO_LARGE error.
Frame size errors in frames that affect connection-level state MUST
be treated as a connection error (Section 5.4.1).
Section 6.7:

Receipt of a PING frame with a length field value other than 8 MUST
be treated as a connection error (Section 5.4.1) of type
PROTOCOL_ERROR.
I propose to simply omit the second one, or just reference the former
section.
==========

See https://github.com/http2/http2-spec/issues/246 for the rest of the
discussion.
Received on Tuesday, 17 September 2013 01:18:06 UTC

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