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

Re: Dealing with Invalid UTF-8

From: Roberto Peon <grmocg@gmail.com>
Date: Fri, 16 Aug 2013 09:31:04 -0700
Message-ID: <CAP+FsNfduN1y8iJt3dq=RW7QqJivXJDx_gKSAqzhiVg-KAZJRA@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: James M Snell <jasnell@gmail.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Yup.


On Fri, Aug 16, 2013 at 2:30 AM, Julian Reschke <julian.reschke@gmx.de>wrote:

> On 2013-08-14 00:12, James M Snell wrote:
>
>> https://github.com/http2/**http2-spec/issues/232<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 16:31:31 UTC

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