every-channel/every.channel
1
0
Fork 0
Code Releases Activity Actions 2

wt: patch web-transport-proto header interop for Cloudflare relay

Browse source
This commit is contained in:
every.channel 2026-02-18 01:28:57 -08:00
parent aa4bddcba0
commit 523c601dc3
No known key found for this signature in database
17 changed files with 2567 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

1
evolution/proposals/ECP-0063-cloudflare-moq-webtransport.md
View file

@ -60,6 +60,7 @@ newer draft implementations.
Implementation choice:
- Cloudflare's relay preview currently does **not** support `ANNOUNCE` (namespace-style publishing). `ec-node wt-publish` uses the `moq-lite` publish model via `moq-native` and `moq-mux` (fMP4 ingestion) for Cloudflare relay compatibility.
- On NixOS deployments, we disable `moq-native`'s WebSocket fallback (`MOQ_CLIENT_WEBSOCKET_ENABLED=false`) to ensure WebTransport (QUIC) is used. This avoids the WebSocket path occasionally "winning" the race and then failing MoQ negotiation against the Cloudflare relay, causing rapid reconnect loops.
- For Cloudflare relay interop, we patch `web-transport-proto` to send and accept the standard WebTransport subprotocol negotiation header (`sec-webtransport-protocol`) in addition to the legacy `wt-available-protocols`/`wt-protocol` headers. Without subprotocol negotiation, the relay may not select a `moqt-*` protocol and can close the session immediately after MoQ `SETUP`.
### Share link