Support gRPC over HTTP/3
I'm creating this issue to explore the possibility of developing a spec for gRPC-over-HTTP/3. HTTP/3 is currently an IETF draft, available to view at https://quicwg.org/base-drafts/draft-ietf-quic-http.html. ------ Edit by @ejona86: If you want better browser support, that is probably https://github.com/grpc/grpc/issues/29818 instead of this issue. C++/ObjC/Java have supported Cronet since 2017 or so, which provides HTTP/3. This issue is talking about non-mobile use cases, because mobile already had support when it was created. grpc-dotnet added support for HTTP/3 sometime around 2021. [gRFC G2: gRPC over HTTP/3](https://github.com/grpc/proposal/blob/master/G2-http3-protocol.md); the application-level protocol is essentially the same as with HTTP/2, as gRPC only requires HTTP/1.1 concepts.
Posted by johanbrandhorst on May 23, 2019, 3:14 PM
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
Support gRPC over HTTP/3
I'm creating this issue to explore the possibility of developing a spec for gRPC-over-HTTP/3. HTTP/3 is currently an IETF draft, available to view at https://quicwg.org/base-drafts/draft-ietf-quic-http.html. ------ Edit by @ejona86: If you want better browser support, that is probably https://github.com/grpc/grpc/issues/29818 instead of this issue. C++/ObjC/Java have supported Cronet since 2017 or so, which provides HTTP/3. This issue is talking about non-mobile use cases, because mobile already had support when it was created. grpc-dotnet added support for HTTP/3 sometime around 2021. [gRFC G2: gRPC over HTTP/3](https://github.com/grpc/proposal/blob/master/G2-http3-protocol.md); the application-level protocol is essentially the same as with HTTP/2, as gRPC only requires HTTP/1.1 concepts.
Comments (0)
No comments yet. Start the discussion.