-
-
Notifications
You must be signed in to change notification settings - Fork 413
New issue
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
[💡FEATURE REQUEST]: Support for QUIC or HTTP/3 #926
Comments
Also, if this request is popular, we will add support for sure ASAP :) |
Technically it's still in draft, but Google already using it in production. |
The IETF just published QUIC as RFC 9000, supported by RFC 9001, RFC 9002, and RFC 8999. That means QUIC version 1 is officially formalized, and QUIC deployments will now move away from using temporary draft versions to the newly minted version 1. (HTTP/3, the version of HTTP that runs on QUIC, is following closely behind, and should be published soon.) This news is a big deal, both for the IETF and for the internet ecosystem. |
ref: golang/go#32204 |
Accepted for the |
http/3 is now standardized: https://www.rfc-editor.org/rfc/rfc9114.html EDIT: Since we have a standard now, I'd rather wait for the Go stdlib implementation. |
HTTP(3) crypto/tls accepted: golang/go#44886 |
Hi guys, author of quic-go here 👋. Have you considered using quic-go for QUIC support in roadrunner? quic-go is quite mature at this point. The project has been around for about 8 years, and (among many others) it powers HTTP/3 support in the Caddy web server and QUIC support in IPFS. We’ll actually use the new crypto/tls API (golang/go#44886) linked in the comment above as soon as Go 1.21 is released. I’d be happy to give you some pointers for integrating it, if there’s interest :) |
Hey @marten-seemann 👋🏻 nice to meet you :) |
The quic-go v0.37.x releases now support Go 1.21. |
That's nice, added to the |
Will be added much faster I think, under the new RR |
Are there any plans of replacing quic-go with x/net/quic once it gets stable? |
Hey @readycool 👋 |
Hi guys,
thank you for the project.
Do you plan to implement the QUIC protocol AKA HTTP/3?
I cannot into Golang, but i've found several implementations of QUIC: 1 2 3
According to the article from Uber, this should be a very promising feature.
The text was updated successfully, but these errors were encountered: