> RFC 8441, released on September 2018, tries to fix this limitation by adding support for “Bootstrapping WebSockets with HTTP/2”. It has been implemented in Fi

> RFC 8441, released on September 2018, tries to fix this limitation by adding support for “Bootstrapping WebSockets with HTTP/2”. It has been implemented in Firefox and Chrome. However, as far as I know, no major reverse-proxy implements it. HAProxy supports RFC 8441 automatically. It's possible to disable it, because support in clients tends to be buggy-ish: https://cbonte.github.io/haproxy-dconv/2.4/configuration.html#3.1-h2-workaround-bogus-websocket-clients https://cbonte.github.io/haproxy-dconv/2.4/configuration.htm... Generally I can second recommendation of using SSE / long running response streams over WebSockets for the same reasons as the article.