- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Mon, 01 Aug 2016 11:01:21 +0000
- To: HTTP Working Group <ietf-http-wg@w3.org>, Willy Tarreau <w@1wt.eu>
-------- In message <20160801104405.GA22799@1wt.eu>, Willy Tarreau writes: >> My take is that the data-model and serialization should be general >> and unconstrained, and the constraints be applied in a/the schema >> for each individual header. > >But we're talking about protocol efficiency as well, which passes via >taking into account what we have. We could for example consider the >notion of "extended strings" which are only used for header fields >which are not relevant to the protocol itself (eg: not used in >accept/range/connection/...) and which would allow unicode to be >safely transmitted. It might be used for user-agent if needed. Unicode can already be safely transmitted as UTF-8, problem is that people don't know if it is UTF-8 or ISO8859. The "\U" prefix/escape would solve that efficiently. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Received on Monday, 1 August 2016 11:15:53 UTC