Skip to content

Update :protocol to webtransport-h3 for WebTransport over HTTP/3#1930

Open
jan-ivar wants to merge 1 commit into
whatwg:mainfrom
jan-ivar:wth3
Open

Update :protocol to webtransport-h3 for WebTransport over HTTP/3#1930
jan-ivar wants to merge 1 commit into
whatwg:mainfrom
jan-ivar:wth3

Conversation

@jan-ivar
Copy link
Copy Markdown
Contributor

@jan-ivar jan-ivar commented May 30, 2026

WebTransport over HTTP/3 draft-15 renamed the extended-CONNECT :protocol pseudo-header value from webtransport to webtransport-h3. WebTransport over HTTP/2 keeps webtransport, making it depend on connection.

  • At least two implementers are interested (and none opposed):
    • Firefox: implementing draft-15 in bug 2033974
    • Chromium: …
    • WebKit: …
  • Tested with web-platform-tests: WebTransport WPT exercises the H3 handshake; the draft-15 :protocol value is covered by the server update in bug 2033974.
  • MDN issue / update: N/A (not author-observable).
  • The top of this comment includes a clear commit message.
  • At least two implementers are interested (and none opposed):

Preview | Diff

Comment thread fetch.bs
<p>If <var>request</var>'s <a for=request>mode</a> is "<code>webtransport</code>",
<var>connection</var> is an HTTP/3 connection, and the "<code>:protocol</code>"
pseudo-header associated with <var>request</var>'s <a for=request>method</a> is
"<code>webtransport</code>", then set the "<code>:protocol</code>" pseudo-header to
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is the pseudo-header associated with request's method? I think you just mean associated with request? What other values besides "webtransport" can it have at this point and given the H3 precondition?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants