Re: Unicode escape sequence | Re: draft-ietf-httpbis-header-structure-00, unicode range

On 2016-12-23 17:36, Mark Nottingham wrote:
>> On 23 Dec. 2016, at 11:13 am, Poul-Henning Kamp <> wrote:
>> --------
>> In message <>, Mark Nottingham wri
>> tes:
>>> And, as discussed previously, there aren't a lot of use cases for
>>> non-ASCII header values in standards (because few have a payload that's
>>> exposed to end users), so the reward for taking that risk is
>>> questionable.
>> But isn't that an almost circular[1] argument, when there is no
>> safe standardized way to put non-ASCII into header values in the
>> first place ?
> There is -- RFC5987 encoding. Not pretty or efficient, but implemented and interoperable. Used in Content-Disposition, Link (although not much), and not much else AFAIK (Julian?).

It's used in the new Digest spec, but I don't believe it's implemented yet.

 > ...

Best regards, Julian

Received on Friday, 23 December 2016 17:21:03 UTC