Enable HTTP/3 (QUIC) between Internet and Cloudflare
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 541
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
We currently enable HTTP/1 and HTTP/2 both between Internet and Cloudflare and between Cloudflare and our origin server. Most clients still use HTTP/1.1 to download Node.js binaries, but more than 80 % of requests to /api use HTTP/2. These are typically modern browsers, which likely also support HTTP/3. As discussed in the #nodejs-build channel on Slack, I'd like to also enable HTTP/3 for connections to Cloudflare, which handles 99 % of our traffic.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Cloudflare configuration that controls protocol support for connections from the Internet to Cloudflare, and review the discussion in the #nodejs-build channel for context. Done means HTTP/3 (QUIC) is enabled for that edge connection and can be verified for Node.js traffic without changing the Cloudflare-to-origin protocol settings.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, infrastructure, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100