Dealing with Invalid UTF-8

• From: James M Snell <jasnell@gmail.com>
• Date: Tue, 13 Aug 2013 15:12:29 -0700
• To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
• Message-ID: <CABP7RbeLcWfvskf37zebahwSVPkLUSVSpmzSC-v=QGCymM-o2Q@mail.gmail.com>

https://github.com/http2/http2-spec/issues/232

The current header compression draft states that header field values
are UTF-8. However, the spec says nothing about how to deal with
overlong encodings, invalid UTF-8 octet sequences or valid UTF-8
sequences that encode invalid Unicode codepoints.

I recommend stating that any of these conditions ought to result in an
error. An encoder MUST NOT output any of these; and a decoder ought to
signal a connection error if encountered.

- James

Received on Tuesday, 13 August 2013 22:13:18 UTC