We're currently somewhat lenient when validating a WebTransport request, in order to improve compatibility with older WebTransport implementations.
At some point, we should tighten the validation logic to what the (then) RFC version says. In particular:
We're currently somewhat lenient when validating a WebTransport request, in order to improve compatibility with older WebTransport implementations.
At some point, we should tighten the validation logic to what the (then) RFC version says. In particular:
webtransport-h3as upgrade token, see use webtransport-h3 as the :protocol upgrade token #280ENABLE_WEBTRANSPORTsetting, see use SETTINGS_WT_ENABLED introduced in draft-15 #254