W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2014

Re: h2 header field names

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Thu, 04 Sep 2014 17:07:30 +0000
To: Julian Reschke <julian.reschke@gmx.de>
cc: Jason Greene <jason.greene@redhat.com>, Amos Jeffries <squid3@treenet.co.nz>, ietf-http-wg@w3.org
Message-ID: <21989.1409850450@critter.freebsd.dk>
In message <54088BD2.1030100@gmx.de>, Julian Reschke writes:

>The main reason why I'm concerned about arbitrary binary data is that 
>all of the HTTP APIs I'm aware essentially work on character sequences, 
>not octet sequences (in header fields).

That is my concern too:  Most code handling HTTP today don't expect
to see embedded NUL's, and a lot of it will happily send through
"poison" characters like ESC.

>The lack of a standard encoding in HTTP/1.1 is already a problem;

But we could apply gentle persuasion here:  If we make HPACK work
really well with baser64 (it does, but could be better) a lot of
people will take the hint.  Not everybody, but a lot of them.

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 Thursday, 4 September 2014 17:07:59 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:10 UTC