We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm wondering if http2 support can be skipped and http3 be considered the future aim.
In the short term perhaps, perhaps https://pkg.go.dev/github.com/quic-go/[email protected]/http3 package can be used behind the scenes by fasthttp until it can be natively implemented with a configuration switch in fasthttp.
Caddy uses that package for http3 support.
The text was updated successfully, but these errors were encountered:
https://medium.com/better-programming/http-3-explained-4bc4e7d31c26
https://quic-go.net/docs/http3/server/
https://kmcd.dev/posts/grpc-over-http3/
Sorry, something went wrong.
@pjebs There's no HTTP2 support. I doubt we will see HTTP3
No branches or pull requests
I'm wondering if http2 support can be skipped and http3 be considered the future aim.
In the short term perhaps, perhaps https://pkg.go.dev/github.com/quic-go/[email protected]/http3 package can be used behind the scenes by fasthttp until it can be natively implemented with a configuration switch in fasthttp.
Caddy uses that package for http3 support.
The text was updated successfully, but these errors were encountered: