bagder/http3-explained

How is Websocket planned in HTTP/3

git001 opened this issue · 7 comments

git001 commented

There is a RFC for Bootstrapping WebSockets with HTTP/2 what's the plan for WS in HTTP/3?

quantumsheep commented

For now there is absolutely no information about a potential WebSockets implementation for QUIC. But it may end up being a WebSockets UDP extension with the use of the Sec-Websocket-Extensions header or so.

It's actually being discussed a lot in the QUIC community, but the working group doesn't seem to have started discussions about it.

git001 commented

@quantumsheep thank you

  • ❤️1
lucsoft commented

after 1 1/2 years are there some news? i love the idea to see websockets over udp

bagder commented

It seems "they" work on having "web transport" become the websocket replacement in the future: https://w3c.github.io/webtransport/ So no, no websockets for h3.

  • 👍3
onpaws commented

Thanks for sharing that link @bagder -- exactly the info I was hoping to find

qm3ster commented

WebSocket over real QUIC streams will be here sooner than you can possibly imagine: https://datatracker.ietf.org/doc/rfc9220/

nikolaydimitrov commented

So anyone knows what the current browser behaviour is?
If we already have HTTP3/QUICK connection it is "ignored" and a new HTTP1.1 (TCP) connection is open for the WebSocket?