aioquic_mitmproxy is a fork of aioquic, that is specifically targeted
towards mitmproxy.
If you want to use QUIC and/or HTTP/3 in your Python project, you should use
aioquic instead: https://pypi.org/project/aioquic/
Any code contributions to aioquic should also be submitted directly to
upstream: https://github.com/aiortc/aioquic
aioquic is a library for the QUIC network protocol in Python. It features
a minimal TLS 1.3 implementation, a QUIC stack and an HTTP/3 stack.
QUIC was standardised in RFC 9000 and HTTP/3 in RFC 9114.
aioquic is regularly tested for interoperability against other
QUIC implementations.
To learn more about aioquic please read the documentation.
aioquic has been designed to be embedded into Python client and server
libraries wishing to support QUIC and / or HTTP/3. The goal is to provide a
common codebase for Python libraries in the hope of avoiding duplicated effort.
Both the QUIC and the HTTP/3 APIs follow the "bring your own I/O" pattern, leaving actual I/O operations to the API user. This approach has a number of advantages including making the code testable and allowing integration with different concurrency models.
- QUIC stack conforming with RFC 9000
- HTTP/3 stack conforming with RFC 9114
- minimal TLS 1.3 implementation conforming with RFC 8446
- IPv4 and IPv6 support
- connection migration and NAT rebinding
- logging TLS traffic secrets
- logging QUIC events in QLOG format
- HTTP/3 server push support
aioquic requires Python 3.8 or better.
aioquic comes with a number of examples illustrating various QUIC usecases.
You can browse these examples here: https://github.com/aiortc/aioquic/tree/main/examples
aioquic is released under the BSD license.