HTTP/3 Support
## Current status HTTP/3 support is on the [roadmap](https://hyper.rs/contrib/roadmap/#http3). There is a working [h3 crate](https://github.com/hyperium/h3), and [reqwest](https://docs.rs/reqwest/latest/reqwest/#unstable-features) 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](https://discord.gg/q5mVhMD) to coordinate work. Here's some of the main steps: - [ ] Harden the `h3` crate 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::quic` integration, allowing people to bring their own QUIC. - [ ] Write the `hyper::proto::http3` glue that translates hyper's connection patterns with the `h3` crate.
Posted by uvd on May 24, 2019, 9:57 AM
Tags
Related issues
- Add 65536 size support for maps
- TypeScript 7.1 Iteration Plan
- nvim-treeconfig: upstream nvim-treesitter
- Add the "action" and "method" attributes to <button>
- [FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)
- > We were imposed GitHub for so many exercises!
Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments
support (Software)
Add 65536 size support for maps
TypeScript 7.1 Iteration Plan
nvim-treeconfig: upstream nvim-treesitter
Add the "action" and "method" attributes to <button>
[FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)
> We were imposed GitHub for so many exercises!
Add support for Visual Studio 2026 Integration
Support for Helm v4
HTTP/3 Support
## Current status HTTP/3 support is on the [roadmap](https://hyper.rs/contrib/roadmap/#http3). There is a working [h3 crate](https://github.com/hyperium/h3), and [reqwest](https://docs.rs/reqwest/latest/reqwest/#unstable-features) 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](https://discord.gg/q5mVhMD) to coordinate work. Here's some of the main steps: - [ ] Harden the `h3` crate 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::quic` integration, allowing people to bring their own QUIC. - [ ] Write the `hyper::proto::http3` glue that translates hyper's connection patterns with the `h3` crate.
Comments (0)
No comments yet. Start the discussion.