HTTP/3 Support
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.3k
- Forks
- 1.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 14
Description
Current status
HTTP/3 support is on the roadmap. There is a working h3 crate, and reqwest has unstable HTTP/3 support.
Much work is still needed, and volunteers are welcome.
Besides the issue tracker (which should store durable decisions and their context), there's this h3 Discord channel to coordinate work.
Here's some of the main steps:
- Harden the
h3crate itself, such as fixing any straggling interop issues,
and filling out the spec conformance tags we use for accountability. - Proposal for (initially unstable)
hyper::rt::quicintegration, allowing
people to bring their own QUIC. - Write the
hyper::proto::http3glue that translates hyper's connection
patterns with theh3crate.
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 with the HTTP/3 roadmap and the existing h3 crate, then review the issue's three listed workstreams. Relevant entry points named here are hyper::rt::quic and hyper::proto::http3; coordinate in the h3 Discord channel. Done requires completing a clearly scoped milestone, such as the QUIC integration proposal or HTTP/3 glue, with the listed interop and conformance work addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100