W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2022

Re: support for non-ASCII in strings, was: signatures vs sf-date

From: Roy T. Fielding <fielding@gbiv.com>
Date: Fri, 2 Dec 2022 11:43:26 -0800
Cc: Julian Reschke <julian.reschke@gmx.de>, ietf-http-wg@w3.org
Message-Id: <D43BBAB7-103E-4FE5-948A-57BB17F13468@gbiv.com>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
> On Dec 2, 2022, at 11:18 AM, Poul-Henning Kamp <phk@phk.freebsd.dk> wrote:
> --------
> Roy T. Fielding writes:
>> FWIW, there is nothing technical preventing a requirement that sf fields
>> support UTF-8 by default.
> (... provided they are somehow escaped into USASCII visibility.)

No, I meant UTF-8, as in coded 8-bit unicode. They don't interfere with parsing
when inside a not-yet-standard field-value, whether or not it is a structured field.
They are, of course, not allowed in current sf field values, but I am not aware of
any implementations that invoke an sf parser on unknown fields.

Received on Friday, 2 December 2022 19:43:56 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:44:08 UTC