Re: Do we kill the "Host:" header in HTTP/2 ?

If we're going to a binary protocol, we should be looking at every 
opportunity to get rid of requirements to parse strings.

IMO this means sending each part of a URI separately in its own field.

Adrien


------ Original Message ------
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
To: "Roberto Peon" <grmocg@gmail.com>
Cc: "Ted Hardie" <ted.ietf@gmail.com>; "Adrien W. de Croy" 
<adrien@qbik.com>; "Eliezer Croitoru" <eliezer@ngtech.co.il>; 
"ietf-http-wg@w3.org" <ietf-http-wg@w3.org>; "John C Klensin" 
<john-ietf@jck.com>
Sent: 31/01/2013 11:55:17 a.m.
Subject: Re: Do we kill the "Host:" header in HTTP/2 ?
>Content-Type: text/plain; charset=ISO-8859-1
>--------
>In message 
><CAP+FsNfGocr9S992SQNWfW+K9Rz5f1XZcVkC7AoV5WXmxF+Pcw@mail.gmail.com>, 
>Roberto Peon writes:
>
>>Dropping the host header will inflate the size of bytes on the wire, 
>>to the
>>detriment of latency.
>
>Really ?
>
>I thought we hadn't decided how things would be encoded yet, so how can
>you tell ?
>
>As far as I can see, if we did this to HTTP/1 with no other changes we 
>would;
>
>  Add "http://" ${fqdn}
>
>  Remove "Host: " ${fqdn} CR NL
>
>Which looks like a one byte saving to me ?
>
>>I haven't yet heard of a real performance advantage for dropping it. 
>>Is
>>there one?
>
>High-performance implementations would not have to text-process the 
>entire
>header to find the fqdn they use for routing decisions.
>
>--
>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 Wednesday, 30 January 2013 23:02:41 UTC