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

Re: Rechartering HTTPbis

From: William A. Rowe Jr. <wrowe@rowe-clan.net>
Date: Thu, 26 Jan 2012 03:26:24 -0600
Message-ID: <4F211C40.3020100@rowe-clan.net>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
CC: Amos Jeffries <squid3@treenet.co.nz>, ietf-http-wg@w3.org
On 1/26/2012 2:39 AM, Poul-Henning Kamp wrote:
> In message <3242f7d9fe2f4046819ab4fcbafab251@treenet.co.nz>, Amos Jeffries writ
> es:
> 
>> So how would compression type be embeded in the request-line in a way 
>> not to break HTTP/1.1 servers receiving it?
> 
> First of all, I would not allow different compression types.  It's ZLIB
> and it's mandatory.

Which?  zlib exposes more than one, now.

> Second, we cannot know if the other end is HTTP/1.1 or HTTP/2.0 until
> we see its reply, so the first request would always be in HTTP/1.1 format.

Or OPTIONS * HTTP/2.0\nHost: thathost.com - or its transparent equivalent.

> One way to indicate the shift to compressed HTTP/2.0 would be that
> the first character of the second request is 'Z', and the entire
> connection is compressed from then on.

Byte?  The TCP stack doesn't speak in bytes.  You gained a packet, use it.
Received on Thursday, 26 January 2012 09:27:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:53 GMT