- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Sat, 15 Oct 2016 22:26:04 +0000
- To: Willy Tarreau <w@1wt.eu>
- cc: Martin Thomson <martin.thomson@gmail.com>, Matt Menke <mmenke@google.com>, HTTP Working Group <ietf-http-wg@w3.org>
-------- In message <20161015213519.GA28177@1wt.eu>, Willy Tarreau writes: >And it also helps when headers are duplicated. Below it's becoming >obvious what type of duplication happened, and where : > > Foo1: >blah<, >bar< > Foo2: >blah, bar< True, but that doesn't make me any more well disposed towards header split/concatenation. >> We have three options: >> >> 1. Keep using RFC7230::token for 'identifier' >(...) >> 2. Restrict 'identifier' >(...) >> 3. Let the semantic layer sort it out. >(...) > >> I picked 3 based on 'minimum intrusiveness', but I can live with >> all three. > >And what about #4 consisting in indicating the encoding in the header >field *name* instead That's quite a hack, isn't it ? I'd prefer not to complicate things that way if I can... -- 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 Saturday, 15 October 2016 22:26:30 UTC