- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Mon, 01 Aug 2016 09:57:25 +0000
- To: HTTP Working Group <ietf-http-wg@w3.org>, Willy Tarreau <w@1wt.eu>
-------- In message <20160801085743.GB22715@1wt.eu>, Willy Tarreau writes: >That made me think that most of the header fields I'm seeing do not use >non-ascii characters at all, I'd even say non-printable-ascii. Most of >them contain : > - host names (Host) > - uris (Referer, Location) > - user-agent strings (UA) > - tokens (Connection, Accept, ...) > - numbers > >Thus in fact I'm wondering if it's really worth focusing the efforts on >non-ascii strings instead. 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. -- 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 09:57:49 UTC