Hello folks,
Since IETF 106 in November 2019, I've been working on a side-project fork of Cloudflare quiche that adds Datagram frame support and QuicTransport.
Today, I'm please to say I deployed a quiche equivalent of the QuicTransport test server decribed on the
web.dev blog [1] to
quic-transport://http3.wtf:5020. For testing purposes, I host a very familiar looking test page at
https://http3.wtf/quictransport/client.html. This zone has a publically-trusted certificate and is opted-in to the Origin Trial.
I've noticed some intial bumps when testing my server with the Chromium QuicTransport client in [whatever version of Chromium I downloaded this afternoon from appspot[2]].
1.
If I send "hello" on a bidirectional stream, the server receives data in
STREAM frames on stream id 0 with a total length of 5 (good). The server then receives a
RESET_STREAM frame with stream id=0 error=10c and size=0. The final size
is mismatched, which quiche detects, and thus responds with a CONNECTION_CLOSE.
2. After connecting to http3.wtf, the client will only sit around for 5 seconds before closing the connection with a message about lack of network activity.
3. Any form of connection errors renders the browser client unable to remake connections without a page reload. Sometimes even then it is unable to reestablish connection to the server (I think this might be a server-related issue to, in case anyone decides to test it)
Anyhow, looking forward to ironing things out and making this demo a bit more stable.
Cheers,
Lucas