W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

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

From: Amos Jeffries <squid3@treenet.co.nz>
Date: Fri, 01 Feb 2013 22:47:50 +1300
Message-ID: <510B8F46.20809@treenet.co.nz>
To: ietf-http-wg@w3.org
On 1/02/2013 8:09 p.m., James M Snell wrote:
> One proposal on this particular topic...
>
> We can combine the :scheme, :method, :host and :path header fields 
> into a single :req Header with a compact binary encoding and require 
> that this single header always appear first in request header blocks.
>
> +------------------------------+
> |S|len(method)|method|len(host)|
> +-+-------+----+---------+-----+
> | host  | len(path) |  path  |
> +------------------------------+
>
> S = Single bit, when set, scheme = https, when not set, scheme = http
> len(method) = 7 bit length of method name
> method = name of method
> len(host) = uvarint(host)
> host = host
> len(path) = uvarint(path)
> path = path
>

This makes several assumptions which are false and will cause a lot of 
trouble:
  1) scheme of URI is always http(s)://.
  2) port is always the default scheme port.
  3) there is never a query string attached
  4) there is never a fragment attached

It also ignores that abomination otherwise known as the '*' URI.
IMHO, this is a good loss, we could require OPTIONS method on the '/' 
URI with the current machines hostname or IP do the equivalent and save 
some parser complexity + CPU checking the * cases on every request.


Amos
Received on Friday, 1 February 2013 09:48:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 1 February 2013 09:48:36 GMT