W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2021

Re: Advertising WebSocket support in the HTTPS resource record

From: Stefan Eissing <stefan.eissing@greenbytes.de>
Date: Thu, 21 Oct 2021 10:05:28 +0200
Cc: Ben Schwartz <bemasc@google.com>, Dragana Damjanovic <dragana.damjano@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <50778B84-8CA0-45FC-BA1A-32DC1C50CD73@greenbytes.de>
To: Lucas Pardue <lucaspardue.24.7@gmail.com>


> Am 20.10.2021 um 23:19 schrieb Lucas Pardue <lucaspardue.24.7@gmail.com>:
> 
> That's the exact case I'm thinking about. There might be little value trying to backport connect-udp to H2 for some kinds of services, it might be better to fallback to plain old CONNECT. Meanwhile, someone might have websocket support left as a TODO for HTTP/3. Requiring feature parity across all versions just increases the bar to experimentation or deploying new versions of things.

+1

Some servers are also configurable in their protocol implementations. H1, H2 and H3 implementations may not be aware of each others capabilities. Or a particular implementation's feature is flawed and disabled until patched. It would be good to allow other H* implementations to still be available as fallback.

Stefan
Received on Thursday, 21 October 2021 08:05:45 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 21 October 2021 08:05:46 UTC