Skip to content
QUIC and HTTP/3 implementation in Python
Python C Shell
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.travis [package] move source code to src Nov 2, 2019
docs [http] announce support for h3-23 and hq-23 Sep 12, 2019
examples [examples] add missing type annotation Nov 29, 2019
requirements [docs] reduce API surface May 18, 2019
src/aioquic [tls] fix typing error Nov 29, 2019
tests Drop support for draft-23 Nov 28, 2019
.appveyor.yml [ci] add appveyor configuration Nov 2, 2019
.gitattributes Initial commit Feb 5, 2019
.gitignore ignore some files Aug 10, 2019
.travis.yml [travis] test against python 3.8 final Nov 2, 2019
LICENSE [docs] add license Mar 10, 2019
MANIFEST.in [package] actually install py.typed Nov 2, 2019
README.rst
setup.cfg [qa] drop local type stubs (fixes: #20) Nov 29, 2019
setup.py [package] fix UnicodeDecodeError when reading about.py Nov 29, 2019

README.rst

aioquic

rtd pypi-v pypi-pyversions pypi-l travis codecov black

What is 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 standardisation is not finalised yet, but aioquic closely tracks the specification drafts and is regularly tested for interoperability against other QUIC implementations.

To learn more about aioquic please read the documentation.

Why should I use aioquic?

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.

Features

  • QUIC stack conforming with draft-23
  • HTTP/3 stack conforming with draft-23
  • minimal TLS 1.3 implementation
  • IPv4 and IPv6 support
  • connection migration and NAT rebinding
  • logging TLS traffic secrets
  • logging QUIC events in QLOG format
  • HTTP/3 server push support

Running the examples

aioquic requires Python 3.6 or better, and the OpenSSL development headers.

$ sudo apt install libssl-dev python3-dev

After checking out the code using git you can run:

$ pip install -e .
$ pip install aiofiles asgiref httpbin starlette wsproto

HTTP/3 server

You can run the example server, which handles both HTTP/0.9 and HTTP/3:

$ python examples/http3_server.py --certificate tests/ssl_cert.pem --private-key tests/ssl_key.pem

HTTP/3 client

You can run the example client to perform an HTTP/3 request:

$ python examples/http3_client.py --ca-certs tests/pycacert.pem https://localhost:4433/

Alternatively you can perform an HTTP/0.9 request:

$ python examples/http3_client.py --ca-certs tests/pycacert.pem --legacy-http https://localhost:4433/

You can also open a WebSocket over HTTP/3:

$ python examples/http3_client.py --ca-certs tests/pycacert.pem wss://localhost:4433/ws

License

aioquic is released under the BSD license.

You can’t perform that action at this time.