Published on April 18 2026

WebTransport and HTTP upgrades

Written by uartnet

@uartnet

Published HTTP/3 tunnels carry WebTransport, and WebSocket handling spans the full upstream HTTP matrix.

For browser-facing real-time systems, this keeps WebTransport on the standard HTTP tunnel path. Sessions can stay on published HTTP endpoints and keep the HTTP policy model at the edge, including token authentication, rstream Auth, and access policies, instead of moving to raw QUIC endpoints just to obtain streams and datagrams.

WebTransport is available on published HTTP tunnels configured for h3. WebSocket support now covers H1, H2C, and H3 upstreams, with protocol translation handled at the edge between downstream and upstream HTTP versions.

The main operational change here is WebTransport on the HTTP tunnel model. The broader WebSocket compatibility closes gaps for HTTP/2 and HTTP/3 upstream services at the same time.

The related CLI workflows are supported by rstream Go CLI 1.11.0 and later.

For the protocol matrix and setup details, refer to Connection Upgrades.