Skip to main content

Implementation of the Digest HTTP headers according to RFC 3230.

Project description

Test Coverage Versions

Introduction

A small library to provide the server and client side methods to require, negotiation and generate Digest HTTP headers as per RFC 3230. Clients can generate Digest headers of the form: Digest: SHA-256=xyz, MD5=abc. Server can require certain algorithms by sending Want-Digest headers of the form: Want-Digest: SHA-256, SHA;q=0.5, MD5;q=0.

Installation

Install using pip:

pip install rfc3230-digest-headers

Overview of the protocol

The protocol works as follows:

  1. Client and server agree on what the instance bytes are for the endpoint in question. Usually the request body or the content of the resource before applying transformations.
  2. Client sends request
  3. If the client did not directly send a valid Digest, the server responds with Want-Digest header to indicate which algorithms it supports.
    • Form of the Want-Digest header: Want-Digest: SHA-256, SHA;q=0.5, MD5;q=0
    • The server can specify qvalues to indicate preference of algorithms.
    • No value equals q=1.0.
    • q=0 means "do not use this algorithm".
  4. Client generates Digest header using one of the supported algorithms and sends it in the request.
    • Form of the Digest header: Digest: SHA-256=xyz, MD5=abc
  5. Server verifies the Digest header and processes the request.

Usage

The library provides only one enum class, DigestHeaderAlgorithm, which can be used by server and client to fully specify, negotiate and generate Digest HTTP headers. You do not use these algorithms directly, but instead have to use a couple of static methods provided by the enum class.

Example: Generate a Digest header

The client generates a Digest for their instance.

from rfc3230_digest_headers import DigestHeaderAlgorithm

instance_bytes = b"Hello, World!"
header = DigestHeaderAlgorithm.make_digest_header(
    instance=instance_bytes,
    algorithms=[DigestHeaderAlgorithm.SHA256, DigestHeaderAlgorithm.MD5]
)
print(header.header_name)  # "Digest"
print(header.header_value) # "SHA-256=..., MD5=..."

Usage: Verify a Digest header

The server receives a request with a Digest header and verifies it.

from rfc3230_digest_headers import DigestHeaderAlgorithm

instance_bytes = b"Hello, World!"
request_headers = {"Digest": "SHA-256=..., MD5=..."}
is_valid, want_digest_header_should_be_added = DigestHeaderAlgorithm.verify_request(
    request_headers=request_headers,
    instance=instance_bytes,
    qvalues={
        DigestHeaderAlgorithm.SHA256: 1.0,
        DigestHeaderAlgorithm.SHA: 0.5,
        DigestHeaderAlgorithm.MD5: 0.0 # If the client sends MD5, they will receive an error
    },
)
print(is_valid)  # True if the Digest header is valid
print(want_digest_header_should_be_added)  # None if valid, otherwise contains the `Want-Digest` header to be sent to the client for negotiation

Usage: Server-side negotiation of algorithms

The server can indicate which algorithms the endpoint requires by sending a Want-Digest header. The header is automatically generated when attempting to verify invalid request headers. In the following example, the client sends a Digest header with an unsupported algorithm (MD5 with a q-value of 0.0), so the server responds with a Want-Digest header indicating which algorithms are supported.

from rfc3230_digest_headers import DigestHeaderAlgorithm

# Fake request from client without an invalid Digest header
instance_bytes = b"Hello, World!"
request_headers = {"Digest": "SHA-256=..., MD5=..."}
is_valid, want_digest_header_should_be_added = DigestHeaderAlgorithm.verify_request(
    request_headers=request_headers,
    instance=instance_bytes,
    qvalues={
        DigestHeaderAlgorithm.SHA256: 1.0,
        DigestHeaderAlgorithm.SHA: 0.5,
        DigestHeaderAlgorithm.MD5: 0.0 # If the client sends MD5, they will receive an error
    },
)
if want_digest_header_should_be_added:
    print(want_digest_header_should_be_added.header_name)  # "Want-Digest"
    print(want_digest_header_should_be_added.header_value) # "SHA-256, SHA;q=0.5, MD5;q=0"
    # Send the response with the generated Want-Digest header
    ...

Usage: Client-side negotiation of algorithms

When an endpoint responds with a Want-Digest header, the client can parse it and generate a valid Digest header. In the following example, imagine that we initially sent a request with b'Hello, World!' as body, and the server responded with an HTTP error code and a Want-Digest header. The client sees that its original request failed, and that the server wants a Digest header. The client then generates a valid Digest header using the highest priority algorithm from the Want-Digest header and re-sends the request.

from rfc3230_digest_headers import DigestHeaderAlgorithm

# Fake response from server with Want-Digest header
instance_bytes = b"Hello, World!"
want_digest_header_value = "SHA-256, SHA;q=0.5, MD5;q=0"

# Option 1: Use make_digest_header with the want_digest_header parameter
# This will automatically handle negotiation
header = DigestHeaderAlgorithm.make_digest_header(
    instance=instance_bytes,
    algorithms="auto",  # Use the highest priority algorithm from Want-Digest
    want_digest_header=want_digest_header_value
)
print(header.header_name)   # "Digest"
print(header.header_value)  # "sha-256=..."

# Option 2: Explicitly use handle_want_digest_header (legacy approach)
header = DigestHeaderAlgorithm.handle_want_digest_header(
    instance=instance_bytes,
    want_digest_header=want_digest_header_value,
    algorithms="auto"  # Use the highest priority algorithm from Want-Digest
)
print(header.header_name)   # "Digest"
print(header.header_value)  # "sha-256=..."

# re-send the request with the generated Digest header
...

You can also use algorithms="all" to include all acceptable algorithms from the Want-Digest header, or provide an explicit list like algorithms=[DigestHeaderAlgorithm.SHA256, DigestHeaderAlgorithm.MD5] to only use specific algorithms that you support.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

rfc3230_digest_headers-1.0.5.tar.gz (8.3 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

rfc3230_digest_headers-1.0.5-py3-none-any.whl (9.4 kB view details)

Uploaded Python 3

File details

Details for the file rfc3230_digest_headers-1.0.5.tar.gz.

File metadata

  • Download URL: rfc3230_digest_headers-1.0.5.tar.gz
  • Upload date:
  • Size: 8.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for rfc3230_digest_headers-1.0.5.tar.gz
Algorithm Hash digest
SHA256 630ce41a43082cb819f4033e25b8ed819f3ff782262ea5ca3f0a2071df5d1c2a
MD5 60fad20904c8323ac56a4d1b9c144629
BLAKE2b-256 830a3703516abf09938c662d8c6e314a530024ace5fa052639877be47f9996b2

See more details on using hashes here.

Provenance

The following attestation bundles were made for rfc3230_digest_headers-1.0.5.tar.gz:

Publisher: publish.yml on Mari6814/py-rfc3230-digest-headers

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file rfc3230_digest_headers-1.0.5-py3-none-any.whl.

File metadata

File hashes

Hashes for rfc3230_digest_headers-1.0.5-py3-none-any.whl
Algorithm Hash digest
SHA256 a35c59f7464d836aeb062fc789b543a99056f89b6526117d978d5ddf170819a7
MD5 46a0c11e91aae4698d7c2720a23848c5
BLAKE2b-256 eaf1e578445ef1c3964cf4a9c7dec40f568fd46b73d6a07d6be2a0b028f14d53

See more details on using hashes here.

Provenance

The following attestation bundles were made for rfc3230_digest_headers-1.0.5-py3-none-any.whl:

Publisher: publish.yml on Mari6814/py-rfc3230-digest-headers

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page