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

Re: draft-ietf-httpbis-jfv: what's next

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>
Message-ID: <80098.1476570364@critter.freebsd.dk>
--------
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

This archive was generated by hypermail 2.3.1 : Saturday, 15 October 2016 22:26:33 UTC