- From: Willy Tarreau <w@1wt.eu>
- Date: Thu, 26 Jan 2012 10:37:48 +0100
- To: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Cc: "William A. Rowe Jr." <wrowe@rowe-clan.net>, Amos Jeffries <squid3@treenet.co.nz>, ietf-http-wg@w3.org
On Thu, Jan 26, 2012 at 09:32:57AM +0000, Poul-Henning Kamp wrote: > >Or OPTIONS * HTTP/2.0\nHost: thathost.com - or its transparent equivalent. > > The problem with that is that if it is a HTTP/1.1 only server, you loose > a round-trip or worst case a connection. > > All clients will have to cope with HTTP/1.1-only servers for ages, > so making the first request on a connection always be HTTP/1.1, and > then if/when the reply indicates HTTP/2.0 capability, upgrade to 2.0 > avoids wasting a round-trip. Indeed, and you also benefit from the existing TCP congestion window. Willy
Received on Thursday, 26 January 2012 09:38:45 UTC