Skip to content

RFC 238: Websocket over HTTP/3 test server#238

Open
Patil-Mayur wants to merge 1 commit into
web-platform-tests:mainfrom
Patil-Mayur:websocket_h3
Open

RFC 238: Websocket over HTTP/3 test server#238
Patil-Mayur wants to merge 1 commit into
web-platform-tests:mainfrom
Patil-Mayur:websocket_h3

Conversation

@Patil-Mayur
Copy link
Copy Markdown

@Patil-Mayur Patil-Mayur commented May 13, 2026

Hi web-platform-tests,

We propose introducing a new test server for WebSocket over HTTP/3 to enable writing corresponding WPTs.
Preview version

Experimental CL for reference which is following this doc changes: https://chromium-review.googlesource.com/c/chromium/src/+/7835151

FYI
@bashi , @ricea, @nidhijaju

@Patil-Mayur Patil-Mayur marked this pull request as ready for review May 13, 2026 07:58
@gsnedders gsnedders changed the title RFC 85: Websocket over HTTP/3 test server RFC 238: Websocket over HTTP/3 test server Jun 2, 2026
Copy link
Copy Markdown
Member

@gsnedders gsnedders left a comment

Choose a reason for hiding this comment

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

Especially given this doesn't actually add any new dependencies, and when this shouldn't be a significant amount of code, I'm not even sure this is really RFC worthy.

Experimental CL for reference which is following this doc changes: https://chromium-review.googlesource.com/c/chromium/src/+/7835151

I do think it might be worthwhile going through the review within the WPT project, rather than doing it in Chromium and relying on upstreaming, because I think the interesting questions are really all specific implementation ones?

Comment thread rfcs/websockets_http3.md

`wptrunner` should recognize `h3` tests but keep them disabled unless H3 support is explicitly enabled, for example with `--enable-h3`. When enabled, `wptrunner` includes those tests, and `wptserve` launches and monitors the WebSocket over HTTP/3 server.

Chromium should use the configured H3 port and force QUIC for that origin.
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.

I don't think how Chromium should be configured it really a relevant part of the question from a WPT point of view, unless it's something particularly complex?

Comment thread rfcs/websockets_http3.md

The main risks are the extra opt-in daemon, the adapter between asynchronous HTTP/3 streams and pywebsocket3's synchronous handler API, and keeping static-resource behavior aligned with `wptserve`.

The Web Networking and Ecosystem Infra owners should maintain the integration point and server behavior.
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.

Most of the actual WPT tooling is maintained, in principle, by WPT organisationally — knowing there are people willing to help is significant, but not a major point.

And also: this should be clear that these are Chromium teams.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants