Re: Dealing with Invalid UTF-8

On 2013-08-14 00:12, James M Snell wrote:
> 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.

...whether this is an issue or not depends on what we decide we respect 
to whether field values are octet sequences or strings...

Best regards, Julian

Received on Friday, 16 August 2013 09:31:41 UTC