Question regarding RFC 8441

• From: Anmol Sethi <hi@nhooyr.io>
• Date: Fri, 05 Apr 2019 07:10:38 +0000
• To: ietf-http-wg@w3.org
• Message-Id: <510B7608-2B9F-405A-81B0-EAD1FF8E03BB@nhooyr.io>

RFC 8441 doesn’t allow clients to gracefully begin using WebSocket’s over HTTP/2.

The only option right now will be to make a CONNECT request over a HTTP/2 connection first to see if the client supports WebSockets over HTTP/2 and then if not, close the connection and fallback to HTTP/1.1.

This is unideal because at least for now, most of the time WebSockets will only be available over HTTP/1.1 so the extra request will just add latency.

I propose a new protocol ID be added to the ALPN list at https://www.iana.org/assignments/tls-extensiontype-values/tls-extensiontype-values.xhtml#alpn-protocol-ids

This will allow a client to efficiently check the TLS handshake to see whether a server supports WebSocket’s over HTTP/2.

Received on Saturday, 6 April 2019 22:44:18 UTC