-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
HTTP/3 Support #2378
HTTP/3 Support #2378
Conversation
A few issues.... aioquic missing from deps, ugly tracebacks when mkcert is not installed and then
Uninstall and reinstall, or maybe just restart fixed the KeyError. Likely some other version of Sanic messing it up. I'll report more soon. |
Seems to be working with curl3, although only serving HTTP/3 prevents browsers from connecting it. I gather this is supposed to multi-serve HTTP1 as well? |
Yeah of course, there is another PR where I am working out how that api should look. |
OH there are a lot more than a few issues 😆 Enough that's it probably not even worth calling out bugs yet because it's no where near an acceptable working version. At this stage it's still a question of architecture and structure. |
Still adding some more tests to get better coverage, but the core of the PR is operational and is ready for some 👀. |
This PR is meant to primarily add HTTP/3 support using the QUIC protocol over UDP. This implementation will use aioquic to create the server.
Getting started
Currently, the best way to start in HTTP/3 mode is as follows:
Starting in
DEBUG
mode will autogenerate a localhost TLS using mkcert or trustme. You will need to have a HTTP/3 capable client.This only introduces support for HTTP requests, an we will release the feature as still "experimental". HTTP/3 support for websockets and webtransport is not yet included. That will probably come later this Summer.