- From: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
- Date: Wed, 17 Apr 2013 14:39:26 +0300
- To: Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
- Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
On Wed, Apr 17, 2013 at 01:15:34AM +0000, Gabriel Montenegro wrote: > http://http2.github.io/http2-spec/#known-http says: > > A client can learn that a particular server supports HTTP/2.0 by other > means. A client MAY immediately send HTTP/2.0 frames to a server that > is known to support HTTP/2.0. This only affects the resolution of "http:" > URIs, servers supporting HTTP/2.0 are required to support protocol > negotiation in TLS<http://http2.github.io/http2-spec/#TLSNPN> [TLSNPN]. > > The above fails to include "https:" URIs. It only mentions "http:" URIs. HTTPS is over TLS, so NPN (ALPN) is a requirement and will reveal if server supports HTTP2 without additional RTTs. -Ilari
Received on Wednesday, 17 April 2013 11:39:54 UTC