NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI
PyPI, #2041 most downloaded on PyPI
An implementation of QUIC and HTTP/3
Latest stable
1.7.2
Last release 20 days ago
02 Nov 2026
Release timing varies
gaps range from 1 weeks to 1.3 years
Rarely documented
notes for 11 of 53 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
53 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
- Fix data written to a stream returned by create_stream() being truncated when it was a memoryview whose items are wider than one byte.
Fix data written to a stream returned by create_stream() being truncated when it was a memoryview whose items are wider than one byte.
Improve type annotations: all functions in the library are now annotated.
Fix the demo application with Starlette 1.0.
Remove the SiDUCK example, as the draft it implemented expired without being adopted.
- Fix streams which never ended when their FIN, written after all their data had been sent, did not fit in the packet being built: the FIN was never s
Fix streams which never ended when their FIN, written after all their data had been sent, did not fit in the packet being built: the FIN was never sent, so the peer kept waiting for it.
Derive the keys for QUIC version 2 key updates with the quicv2 ku label, as RFC 9369 requires. After its first key update, a QUIC version 2 connection could no longer exchange packets with a conforming peer.
Reject a FIN or RESET_STREAM whose final size is below the data already received with FINAL_SIZE_ERROR , as RFC 9000 recommends, instead of silently discarding the data beyond it.
Drop 1-RTT packets which a server receives on a connection ID it never issued or which the client retired, as RFC 9000 requires, instead of switching to that connection ID.
Discard Retry packets which a client receives after processing a packet from the server, or whose Retry Token is empty, as RFC 9000 requires. Such a Retry restarted the connection attempt, and broke an established connection.
Discard 0-RTT keys once 1-RTT keys are in use, as RFC 9001 requires: on servers when the first 1-RTT packet arrives, on clients when they install 1-RTT keys.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
- Migrate clients to the server’s preferred address, as RFC 9000 allows.
Migrate clients to the server’s preferred address, as RFC 9000 allows.
Note
If you drive QuicConnection with your own I/O, you must send each datagram to the address returned alongside it by datagrams_to_send() . That address may now differ from the one passed to connect() , so a connected UDP socket or a tunnel with a single fixed destination no longer works.
Add get_peer_address() , which returns the address datagrams are currently sent to. It can change when either endpoint migrates.
Improve path validation and connection migration as RFC 9000 requires:
Discard datagrams received by clients from unknown server addresses.
Pad datagrams carrying PATH_CHALLENGE or PATH_RESPONSE frames to 1200 bytes, within the anti-amplification limit.
Retransmit lost PATH_CHALLENGE frames on servers, abandon failed validations and revert to the last validated address.
Answer path probes on servers on the path they arrive on, with a connection ID kept for each path.
Keep outstanding PATH_CHALLENGE data for each path, and ignore a PATH_RESPONSE that matches no challenge instead of closing the connection.
Keep clients on the preferred address when the server probes them from its original address.
Reset the spin bit when changing connection ID.
Grant MAX_STREAMS credit as the peer’s streams close, instead of whenever half the limit was used, so the stream limit bounds concurrency. Stream IDs an application skips can no longer be used later.
Restart the idle timer when sending the first ack-eliciting packet after receiving one, as RFC 9000 requires.
Fix handshakes stalling or failing:
Pad datagrams carrying INITIAL packets to 1200 bytes even when the congestion window is full, as RFC 9000 requires. A client sending 0-RTT data could send short datagrams, which servers discard.
Acknowledge 0-RTT packets before the handshake completes, as RFC 9000 requires.
Send lost HANDSHAKE data even when the congestion window is full, instead of stalling until the idle timeout when no probe timer was armed.
Only assume the server’s INITIAL packets were lost while the client is waiting for the ServerHello, as RFC 9002 describes, instead of sending spurious probes for packets it cannot decrypt later on.
Do not arm the ACK timer or the probe timeout while the anti-amplification limit leaves no room to send, as RFC 9002 requires. A server answering a 0-RTT request could otherwise busy loop until the client sent again, or until the idle timeout.
Stop servers from exceeding the anti-amplification limit by one byte when a packet’s only frame is a single byte, such as a PING.
Improve ACK frame handling as RFC 9000 requires:
Reject ACK frames containing negative packet numbers with FRAME_ENCODING_ERROR .
Keep at most 64 ACK ranges, and leave out the oldest ranges which do not fit in an ACK frame.
Lower the cost of processing ACK frames, which now grows with the number of ranges and of newly acknowledged packets, not of packets in flight.
Encrypt retry tokens with AES-GCM instead of RSA, which makes validating them much cheaper. Only accept a token on the Retry packet’s connection ID and for 30 seconds, to limit replays as RFC 9000 requires.
Support interim (1xx) responses in HTTP/3. A final response which follows them is no longer rejected as trailers.
Reject HTTP/3 messages containing connection-specific header fields, and only allow TE: trailers , as RFC 9114 requires.
Abort HTTP/3 request streams with H3_REQUEST_INCOMPLETE when they end before their HEADERS frame, instead of keeping them until the connection closes.
Skip interim responses in the httpx example.
- Fix handshakes stalling under packet loss:
Fix handshakes stalling under packet loss:
Install the client’s Handshake write key on receiving the ServerHello, as RFC 8446 and RFC 9001 allow. If the server’s EncryptedExtensions was lost, the client could not acknowledge the server’s Handshake packets, which deadlocked against servers whose probes carry no data.
Retransmit the oldest unacknowledged packet’s data when the PTO fires, instead of sending a bare PING, as RFC 9002 recommends. Lost data such as HANDSHAKE_DONE or a request’s STREAM frame no longer waits for the probe’s acknowledgement to be retransmitted.
Stop treating a PTO expiry or a CRYPTO data retransmission as a congestion event, as RFC 9002 requires.
Fail pending requests and WebSocket reads in the http3_client example when the connection terminates, instead of waiting indefinitely.
- Abort the TLS handshake with an alert, instead of raising an exception which left the connection hung, when the peer sends a malformed certificate,
Abort the TLS handshake with an alert, instead of raising an exception which left the connection hung, when the peer sends a malformed certificate, a certificate whose key cannot be loaded, a CertificateVerify algorithm which does not match its key, a ClientHello or ServerHello without a key share, a server name which is not ASCII, or an empty Certificate message.
Only use RSASSA-PSS for RSA signatures in CertificateVerify and reject PKCS#1 v1.5 signatures from the peer, as RFC 8446 requires.
Close the connection with no_application_protocol when ALPN negotiation fails, including when the server selects no protocol, several protocols or one the client did not offer.
Fix session resumption failing with a BufferWriteError when the session ticket or the key share is large, such as with X25519MLKEM768.
Send session tickets only after the client’s Finished. A client which never completed the handshake could make the server retransmit them indefinitely.
Harden connection establishment as RFC 9000 and RFC 9001 require:
Close the connection with INVALID_TOKEN when a Retry token is invalid, instead of leaving the client waiting for its idle timeout.
Discard packets whose Source Connection ID differs from the server’s first Initial, and Retry packets reusing the original Destination Connection ID.
Treat a non-empty legacy_session_id in the ClientHello as a PROTOCOL_VIOLATION .
Reject initial_max_streams transport parameters above 2^60.
Defer key updates requested before the handshake is confirmed.
Improve loss recovery and congestion control as RFC 9002 requires: do not arm the PTO for application data before the handshake is confirmed, keep the client’s PTO backoff until the server has validated its address, and collapse the congestion window on persistent congestion.
Discard locally-initiated unidirectional streams once they finish, instead of keeping them until the connection closes. Sending data on a stream which has been discarded now raises ValueError instead of silently creating a new stream.
Answer STOP_SENDING with a RESET_STREAM carrying the peer’s error code.
Check for allocation failure in Buffer and reject a negative capacity with ValueError .
Fix HTTP/3 stream end handling: report the end of a stream when it arrives with a trailing unknown frame or PUSH_PROMISE, instead of never reporting it, and close the connection with H3_FRAME_ERROR when a frame is truncated by the end of the stream, instead of passing off a truncated body as complete.
Fix HTTP/3 server push handling:
Resume a PUSH_PROMISE blocked on QPACK as a PUSH_PROMISE, instead of closing the connection with H3_MESSAGE_ERROR .
Treat MAX_PUSH_ID as the largest allowed push ID, and close the connection with H3_ID_ERROR when a push ID exceeds it or when it is reduced.
Close the connection with H3_STREAM_CREATION_ERROR when a server receives a push stream.
- Fix several ways a peer could make memory usage grow without bound:
Fix several ways a peer could make memory usage grow without bound:
Retire HTTP/3 unidirectional streams once they end, and HTTP/3 streams which are reset or stopped by the peer, or which end while blocked on QPACK.
Stop delivering stream events after a stream’s receiving side has finished, so a duplicate FIN or RESET_STREAM is not reported again.
Forget peer connection ID sequence numbers below retire_prior_to .
When a reset stream is reset again or receives more data, do not count its final size against connection-level flow control a second time. Counting it twice could close a well-behaved peer’s connection with FLOW_CONTROL_ERROR.
Close the connection with H3_FRAME_ERROR when a SETTINGS or PUSH_PROMISE frame is truncated, instead of raising an exception to the application.
Abort the TLS handshake with an illegal_parameter alert when the peer’s key share is invalid, and only accept key shares for groups the server supports.
Stop using assertions to validate data received from the peer, so malformed input closes the connection or drops the packet, including when running with -O .
Raise ValueError for invalid arguments and RuntimeError for calls made in the wrong state, such as writing to a stream after it has ended or been reset, instead of failing an assertion.
Send a QPACK Stream Cancellation when a stream with a blocked header block is reset, and treat resetting or stopping an HTTP/3 control or QPACK stream as a connection error, as RFC 9114 and RFC 9204 require.
Do not send a FIN when closing the writer of a receive-only stream in the asyncio API .
Require pylsqpack 1.0 or later.
- Perform header protection and payload encryption in Python using cryptography instead of a C extension linked to OpenSSL . This fixes memory safety
Perform header protection and payload encryption in Python using cryptography instead of a C extension linked to OpenSSL . This fixes memory safety issues when handling malformed packets, lifts the 1500-byte limit on received packets and removes the need for OpenSSL development headers when building from source.
Discard duplicate packets as required by RFC 9000 section 12.3.
Limit the number of network paths per connection.
Do not reply to Version Negotiation packets with another Version Negotiation packet.
Discard unknown HTTP/3 frames incrementally instead of buffering them.
Handle HTTP/3 frame types as defined by RFC 9114 .
Add support for Python 3.15, drop support for Python 3.10.
- Ensure PATH_CHALLENGE frames are sent before other frame types.
Ensure PATH_CHALLENGE frames are sent before other frame types.
Reclaim memory when HTTP/3 streams end.
Limit the number of remote PATH_CHALLENGE stored per path.
Avoid assertion error when receiving multiple STOP_SENDING frames.
Improve type annotations.
Make it possible to use LibreSSL instead of OpenSSL.
Add support Python 3.13 and 3.14, drop support for Python 3.8 and 3.9.
Build binary wheels for musllinux .
Build binary wheels against OpenSSL 3.5.4.
Add command-line argument to the http3_client example to request a key update during interoperability tests.
- Add support for compatible version handling as defined in RFC 9368 .
Add support for compatible version handling as defined in RFC 9368 .
Add support for QUIC Version 2, as defined in RFC 9369 .
Drop support for draft QUIC versions which were obsoleted by RFC 9000 .
Improve datagram padding to allow better packet coalescing and reduce the number of roundtrips during connection establishement.
Fix server anti-amplification checks during address validation to take into account invalid packets, such as datagram-level padding.
Allow asyncio clients to make efficient use of 0-RTT by passing wait_connected=False to connect() .
Add command-line arguments to the http3_client example for client certificates and negotiating QUIC Version 2.
Add support for compatible version handling as defined in 9368.
Add support for QUIC Version 2, as defined in 9369.
Drop support for draft QUIC versions which were obsoleted by 9000.
Improve datagram padding to allow better packet coalescing and reduce the number of roundtrips during connection establishement.
Fix server anti-amplification checks during address validation to take into account invalid packets, such as datagram-level padding.
Allow asyncio clients to make efficient use of 0-RTT by passing wait_connected=False to ~aioquic.asyncio.connect.
Add command-line arguments to the http3_client example for client certificates and negotiating QUIC Version 2.
- Improve path challenge handling and compliance with RFC 9000 .
Improve path challenge handling and compliance with RFC 9000 .
Limit the amount of buffered CRYPTO data to avoid memory exhaustion.
Enable SHA-384 based signature algorithms and SECP384R1 key exchange.
Build binary wheels against OpenSSL 3.3.0.
- Fix utcnow() deprecation warning on Python 3.12 by using cryptography 42.0 and timezone-aware datetime instances when validating TLS certificates.
Ensure no data is sent after a stream reset.
Make H3Connection ’s send_datagram() and send_push_promise methods raise an InvalidStreamTypeError exception if an invalid stream ID is specified.
Improve the documentation for QuicConnectionProtocol ’s transmit() method.
Fix utcnow() deprecation warning on Python 3.12 by using cryptography 42.0 and timezone-aware datetime instances when validating TLS certificates.
Build binary wheels against OpenSSL 3.2.0.
Ignore any non-ASCII ALPN values received.
Perform more extensive HTTP/3 header validation in H3Connection .
Fix exceptions when draining stream writers in the asyncio API .
Set the QuicConnection idle timer according to RFC 9000 section 10.1.
Implement fairer stream scheduling in QuicConnection to avoid head-of-line blocking.
Only load certifi root certificates if none was specified in the QuicConfiguration .
Improve padding of UDP datagrams containing Initial packets to comply with RFC 9000 section 14.1.
Limit the number of pending connection IDs marked for retirement to prevent a possible DoS attack.
A library for QUIC in Python.
Design
QUIC API
HTTP/3 API
asyncio API
Changelog
1.8.0
1.7.2
1.7.1
1.7.0
1.6.1
1.6.0
1.5.0
1.4.0
1.3.0
1.2.0
1.1.0
1.0.0
License
Documentation overview
Previous: asyncio API
Next: License
©Jeremy Lainé.
| Powered by Sphinx 9.1.1 & Alabaster 1.0.0 | Page source
Ensure no data is sent after a stream reset.
Make ~aioquic.h3.connection.H3Connection's ~aioquic.h3.connection.H3Connection.send_datagram and send_push_promise methods raise an ~aioquic.h3.exceptions.InvalidStreamTypeError exception if an invalid stream ID is specified.
Improve the documentation for ~aioquic.asyncio.QuicConnectionProtocol's ~aioquic.asyncio.QuicConnectionProtocol.transmit method.
Fix ~datetime.datetime.utcnow deprecation warning on Python 3.12 by using cryptography 42.0 and timezone-aware ~datetime.datetime instances when validating TLS certificates.
Build binary wheels against OpenSSL 3.2.0.
Ignore any non-ASCII ALPN values received.
Perform more extensive HTTP/3 header validation in ~aioquic.h3.connection.H3Connection.
Fix exceptions when draining stream writers in the asyncio API.
Set the ~aioquic.quic.connection.QuicConnection idle timer according to 9000 section 10.1.
Implement fairer stream scheduling in ~aioquic.quic.connection.QuicConnection to avoid head-of-line blocking.
Only load certifi root certificates if none was specified in the ~aioquic.quic.configuration.QuicConfiguration.
Improve padding of UDP datagrams containing Initial packets to comply with 9000 section 14.1.
Limit the number of pending connection IDs marked for retirement to prevent a possible DoS attack.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.