Skip to main content

hpke-http for Python

hpke_http protects HTTP requests and replies with the Rust hpke-http/3 engine. Use the HTTPX or aiohttp client with an ASGI app.

Build this checkout

This guide uses the shared key source and HHKD v2 record in this checkout. The published 3.0.0 package does not have this API. Build this checkout first:

make install-deps-python build-python

This installs the HTTPX, aiohttp, and FastAPI extras and builds the Rust binding from this checkout.

Protect an ASGI app

Wrap the app at one HTTPS path:

from hpke_http.middleware.fastapi import HPKEMiddleware

protected_app = HPKEMiddleware(
    app,
    recipient_private_key,
    key_id,
    resolve_psk,
    admit_replay,
    key_use_for_s=lease_seconds,
    transport_path="/protected",
)

resolve_psk(psk_id, scope) returns the PSK for a public ID. It raises LookupError if the ID is unknown. admit_replay(replay_id, deadline, scope) atomically stores a new replay ID until the given exclusive Unix second. It returns True only for the first use. Both callbacks can be async.

The wrapper serves the public key at GET /protected. It accepts protected requests at POST /protected. The transport_path must match the full ASGI path. Set expected_authority if the logical host differs from the outer Host header. A lifespan shutdown closes the native server; call protected_app.close() at shutdown if the host sends no lifespan events. The service sets lease_seconds and a bound to deliver and parse POST START. For a planned switch from A to B, set all workers to advertise A with accepted_keys=[(b_private_key, b_key_id)]. Then set all workers to advertise B with accepted_keys=[(a_private_key, a_key_id)]. After the last A lease, POST START delivery bound, and worker clock margin end, set all workers to advertise B with no other accepted key. Each pair holds a private key, then its public ID.

The app receives its usual HTTP request fields and body. The wrapper checks START, every DATA part, END, and the outer body end before it starts the app. It keeps up to 256 KiB of checked body bytes in memory, then uses a temporary file. The app can send a finite reply or server-sent events (SSE). For SSE, send status 200 and Content-Type: text/event-stream. End each event with a blank line; the wrapper drops an incomplete last block.

For a browser page on another origin, put CORS outside the HPKE wrapper so it can answer the browser's OPTIONS request and add headers to fault replies:

from starlette.middleware.cors import CORSMiddleware

browser_app = CORSMiddleware(
    protected_app,
    allow_origins=["https://app.example.test"],
    allow_methods=["GET", "POST"],
    allow_headers=["cache-control", "content-type"],
    expose_headers=["content-encoding"],
)

The browser must read outer Content-Encoding on GET and POST replies. If a proxy adds this header, CORS must expose it so the client can check it.

Send requests with HTTPX

from hpke_http.middleware.httpx import DiscoveredEndpoint, HPKEAsyncClient

endpoint = "https://api.example.test/protected"
async with DiscoveredEndpoint(endpoint) as key_source:
    async with HPKEAsyncClient(key_source, psk, b"tenant-42") as client:
        response = await client.post("https://api.example.test/items", json={"name": "Ada"})
        response.raise_for_status()
    async with HPKEAsyncClient(key_source, psk, b"tenant-42") as client:
        with open("large.bin", "rb") as file:
            response = await client.post(
                "https://api.example.test/upload",
                files={"upload": file},
            )

The first call sends a key GET and a protected POST. The second sends only a POST while the lease is valid. Keep the source open across client lifetimes.

request() returns a fully checked httpx.Response. Normal HTTPX content, data, json, and files arguments work. The Rust writer reads source bytes as the HTTP library sends them. It groups bytes into request DATA parts of at most 64 KiB. You can also pass an async byte source as content.

For an SSE reply, use stream():

async with client.stream("GET", "https://api.example.test/events") as response:
    async for block in response.iter_sse():
        handle_sse_block(block)

iter_sse() yields each checked, LF-ended byte block. Decode and parse blocks with the SSE rules. For a finite reply in a stream context, call await response.read().

Send requests with aiohttp

import aiohttp
from hpke_http.middleware.aiohttp import DiscoveredEndpoint, HPKEClientSession

form = aiohttp.FormData()
with open("large.bin", "rb") as source:
    form.add_field("upload", source, filename="large.bin")
    async with DiscoveredEndpoint(endpoint) as key_source:
        async with HPKEClientSession(key_source, psk, psk_id) as session:
            async with session.post(logical_url, data=form) as response:
                result = await response.read()

HPKEClientSession accepts bytes, text, form mappings, FormData, async byte sources, and JSON. It keeps the ordinary aiohttp request shape. The finite HPKEResponse has status, headers, read(), text(), json(), and raise_for_status(). Use session.stream() and iter_sse() for SSE.

Technical details

Keys and transport

DiscoveredEndpoint(endpoint) holds one checked key until its service-set use_for_s lease ends. Concurrent callers share one GET. Keep a distinct source for each full endpoint URL, including Bridge and Library paths.

The lease clock starts before GET, so a slow GET leaves less time to start POST. The client checks the lease before POST START. It can get a new key if it can still use the request body; otherwise it reports discovery_expired before it yields POST START. The service's POST START delivery bound covers time after that check.

A source owns its outer HTTP pool and endpoint URL; short-lived credential clients borrow it. Set HTTPX TLS and pool options on the HTTPX source, and aiohttp connector and session options on the aiohttp source. HTTPX client default headers, params, and timeout apply to its logical requests. Each Python source belongs to one event loop. If one caller cancels its wait for a shared GET, the GET continues for other callers. Close each client before you close the source.

get_timeout_s defaults to 10 seconds and limits one key GET. It does not limit the protected POST. Set an HTTPX client or request timeout for POST I/O. With aiohttp, set a source session or request timeout for POST. To limit the full GET and POST call, set an app deadline around the call.

get_key() returns a public hpke_http.middleware.KeyLease with key_id, public_key, and valid(). Check valid() when you use the key, since the lease can end after get_key() returns.

Use PinnedKey(recipient_public_key, key_id) to use a fixed key without a GET. Pass endpoint= with a pin. A shared source supplies its own endpoint URL. Both clients send the protected POST to that URL. Set target_origin="https://api.example.test" if a gateway serves a different logical host. The clients require HTTPS, check the logical target, and do not follow outer redirects. They do not retry a protected POST. The GET has no bearer, cookies, or PSK ID. Business headers stay in the protected request. A lost reply leaves the request result unknown.

HHKD v2 requires a positive lease; these clients have no v1 discovery fallback. A client that reads only HHKD v1 cannot use a v2 host, and a v2 client cannot use a v1 host. Switch clients and hosts together, or use separate endpoints.

Generate a recipient key pair with generate_key_pair(). Recipient keys use X25519 and have 32 bytes. Key and PSK IDs are public opaque values of 1 to 255 bytes. A PSK needs at least 32 bytes of entropy. A Python bytes object cannot be erased in place; keep secret copies to a minimum.

Transport errors

hpke_http.TransportError.code tells callers why an adapter could not finish a protected call:

Discovery code Meaning
discovery_network GET failed or timed out.
discovery_status GET returned a status other than 200.
discovery_response GET headers or key record were invalid.
discovery_expired The lease ended before POST START.

status_code is set for discovery_status and outer_status. Other outer transport failures also raise TransportError; authenticated logical HTTP errors return a normal response. Use response.raise_for_status() to raise on those logical errors. A failed POST is not retried.

Limits and payload coding

Limit Default Hard maximum
Request clear bytes 1 GiB 4 GiB
Finite reply body or one SSE block 8 MiB 64 MiB
Request DATA part 64 KiB 64 KiB
Header name and value bytes 16 KiB 64 KiB
Header fields 64 256
Authority and path bytes 8 KiB 8 KiB

Set Limits(max_request_bytes=...) on both client and server for a service request cap. The HTTPX and aiohttp clients use this stream limit for every request. The low-level Client.protect(Request(...)) helper holds a full body in memory and uses max_body_len (8 MiB by default) as its cap. max_body_len also sets the finite reply and per-SSE-block cap. A host must also set limits for concurrent uploads, upload time, and temporary disk. An ASGI host can deliver one outer event larger than 64 KiB, so that event can use more memory.

Rust selects raw bytes or zstd for each request DATA part, finite reply body, and SSE block, then encrypts it. The recipient checks each tag before it decodes the part. This coding is part of the protected payload; it is not HTTP Content-Encoding.

The protocol does not hide payload size, record count, or timing, and it adds no random padding. HTTPS remains required. The request media type is message/hpke-http-request, and the reply media type is message/hpke-http-response.

Low-level streamed requests

The HTTPX and aiohttp clients send records on their own. For a custom HTTP transport, use the low-level writer. send_part writes one outer POST body part, end_outer_body closes that body, and source supplies byte chunks:

from contextlib import closing
from hpke_http import Client, Method, RequestHead

with closing(Client(recipient_public_key, key_id, psk, psk_id)) as client:
    head = RequestHead(method=Method.POST, authority="api.example.test", path="/upload")
    writer, start = client.begin_stream(head)
    response_right = None
    try:
        await send_part(start)
        async for chunk in source:
            offset = 0
            while offset < len(chunk):
                used, record = writer.push(chunk[offset:])
                if used == 0 and record is None:
                    raise RuntimeError("request writer made no progress")
                offset += used
                if record is not None:
                    await send_part(record)
        end, response_right = writer.finish()
        await send_part(end)
        await end_outer_body()
    except BaseException:
        if response_right is not None:
            response_right.close()
        raise
    finally:
        writer.close()

Use response_right to check the reply, then close it.

OpenedStreamRequest.feed() yields checked DATA parts. Store those parts until END and the outer body end pass. Then finish_eof() returns a StreamResponseRight, which can protect one reply. It has no request body; use the checked parts and OpenedStreamRequest.head to dispatch the request.

Runtime support

The package supports CPython 3.10 through 3.14. Wheels target Linux x86-64 and AArch64 and macOS universal2. Other Linux and macOS CPython targets need a Rust source build. Windows and PyPy are not supported.

Release files for hpke-http 4.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for hpke-http 4.0.0
File Size Uploaded
hpke_http-4.0.0.tar.gz 114.7 kB Details

Built distributions (wheels)

Table of built distributions (wheels) for hpke-http 4.0.0
File Interpreter ABI Platform
hpke_http-4.0.0-cp310-abi3-manylinux_2_28_x86_64.whl CPython 3.10 abi3 Linux glibc 2.28+ x86-64 Details
hpke_http-4.0.0-cp310-abi3-manylinux_2_28_aarch64.whl CPython 3.10 abi3 Linux glibc 2.28+ ARM64 Details
hpke_http-4.0.0-cp310-abi3-macosx_10_12_x86_64.macosx_11_0_arm64.macosx_10_12_universal2.whl CPython 3.10 abi3 macOS 11.0+ ARM64, macOS 10.12+ x86-64, macOS 10.12+ universal2 (ARM64, x86-64) Details

Total release size: 2.3 MB

Release files / hpke_http-4.0.0.tar.gz

Download URL hpke_http-4.0.0.tar.gz
Size 114.7 kB
Tags Source
SHA-256 checksum
How to use checksums
75c78e45c82de6ef3e34c774149518ee456830653f993b8ab8187e8c88e5d9cf
BLAKE2b-256 checksum
How to use checksums
6fcf0ec909ae9645a3664297f5ccc1d80e5bb9f144ea63b8d7f119a2e0604b87
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release files / hpke_http-4.0.0-cp310-abi3-manylinux_2_28_x86_64.whl

Download URL hpke_http-4.0.0-cp310-abi3-manylinux_2_28_x86_64.whl
Size 589.6 kB
Tags CPython 3.10 Linux glibc 2.28+ x86-64 abi3
SHA-256 checksum
How to use checksums
b9311ae7bf1a27d5a3fee7064e2b7f7223f6d2db158706653afdfcccbd487aa2
BLAKE2b-256 checksum
How to use checksums
e70a80a800bbd94afe0e91e02c99a324600af9318e8f4959f3b6730876dd9426
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release files / hpke_http-4.0.0-cp310-abi3-manylinux_2_28_aarch64.whl

Download URL hpke_http-4.0.0-cp310-abi3-manylinux_2_28_aarch64.whl
Size 568.4 kB
Tags CPython 3.10 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
6d0626e5616b69e6f819d40a487e9a73aa2026eeec2638c187edeac8808d6c27
BLAKE2b-256 checksum
How to use checksums
dafa17c615db62a68b4f13fbfa4e7089f08b1dff6952a3997c671b3bfdd96f43
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release files / hpke_http-4.0.0-cp310-abi3-macosx_10_12_x86_64.macosx_11_0_arm64.macosx_10_12_universal2.whl

Download URL hpke_http-4.0.0-cp310-abi3-macosx_10_12_x86_64.macosx_11_0_arm64.macosx_10_12_universal2.whl
Size 983.0 kB
Tags CPython 3.10 abi3 macOS 10.12+ universal2 (ARM64, x86-64) macOS 10.12+ x86-64 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
1e6a8bb845d333bee210e617328e9ca40487555329de93d5ecfb5f3d0020e0c5
BLAKE2b-256 checksum
How to use checksums
f95c22be367f36a05b7b07e821757acb0062e9b77fa5b39aa182f6f5e6be189f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

4.0.0 This release

4 release files

3.0.0

4 release files

2.1.1

4 release files

2.1.0

4 release files

2.0.2

4 release files

2.0.1

4 release files

2.0.0

4 release files

1.6.1

2 release files

1.6.0

2 release files

1.5.0

2 release files

1.4.0

2 release files

1.3.0

2 release files

1.2.0

2 release files

1.1.0

2 release files

1.0.1

2 release files

1.0.0

2 release files

0.1.2

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page