Testing against Google, Cloudflare, Facebook and Microsoft
Every big QUIC deployment is a slightly different interpretation of the RFCs. Here is what each one taught us.
Writing a QUIC client against your own server proves very little: both sides share your misreadings of the spec. The real test is the public internet, where four or five independent implementations answer.
The lineup
- Cloudflare (quiche, Rust) — the most forgiving; a good first target.
- Google — fast to close connections that misbehave, which surfaces timing bugs quickly.
- Facebook (mvfst, C++) — answers with a redirect, which exercises the full request/response path.
- Microsoft (msquic) — sends a HelloRetryRequest when the key share does not match, a path many clients never test.
- nginx QUIC — a common self-hosted server and a good sanity check.
Reproduce it
shell
node examples/client.js https://cloudflare-quic.com/
node examples/client.js https://www.google.com/
node examples/client.js https://outlook.office.com/The results table on the home page is the current state; when one of them changes behaviour, that row is the first thing we update.