Shaduf.Research preview
HTTP Cache Field Guide/Digest-field association

Reader guide · 9 Nov 2026 · digest association

Do cache operations keep a digest attached to the right bytes?

Keep three scopes separate: the content in this message, the complete coded representation, and the complete decoded representation. RFCs define the fields and general cache operations; a current Internet-Draft proposes extra digest-association safeguards.

Standards and draft-text review only. No cache, endpoint, provider, browser, or implementation was tested.

Short answer

A digest field is useful only with its defined input. Content-Digest covers this message’s content; Repr-Digest covers the whole selected representation in its coded form; and Unencoded-Digest covers the whole representation after content codings are removed, as defined by a separate work-in-progress draft. RFC 9111 still governs cache update, 304/HEAD freshening, and range operations. A non-adopted cache-integrity draft proposes that a cache preserve the correct association, recalculate over the resulting input, or remove the member after those operations.

Three byte scopes, not three names for one checksum

Content-Digest

Input: exact content bytes in this message (RFC 9530 §2).

For a 206, this can be one range or multipart content. A 304 or HEAD has no content, so its input is empty. It does not automatically describe the stored full GET body.

Repr-Digest

Input: the entire selected representation (RFC 9530 §3), in coded form when a content coding is applied.

It can describe the full representation when the message carries a range or no content, provided the association is known.

Unencoded-Digest

Input: the full selected representation after all content codings are removed, from draft-ietf-httpbis-unencoded-digest-05 §3. This definition was WIP—not RFC 9530—in the 9 Nov 2026 review.

Keep today’s RFC rules separate from a proposal

Published RFCs

What currently governs cache operations

RFC 9111 §3.2 specifies general stored-field updates. §§4.3.4–4.3.5 cover 304 and HEAD freshening. §§3.3–3.4 cover partial storage and range combination. RFC 9530 defines the two published digest fields.

Work in progress

What the cache-integrity draft adds

draft-jurkovikj-http-integrity-cache-00 proposes per-member association safeguards. It is an initial individual Internet-Draft, not an adopted RFC; the cover’s intended status does not change that.

The draft does not replace RFC 9111’s selection of stored responses for a 304 update or its conditions for a HEAD update. It proposes separate handling for each digest member after the ordinary cache operation is determined.

A quick operation check

When the cache…Check the member against…Do not assume…
updates stored fields from a 304 or HEADThe exact retained message content for Content-Digest; the complete selected representation for representation digests.A bodyless updater’s empty-content digest describes non-empty retained GET bytes. RFC 9111’s Last-Modified or Content-Length pathway is not automatically a digest witness.
combines partial responsesThe resulting content for Content-Digest; eligible complete-representation evidence for the other two.A strong validator alone makes a range-content digest describe a combined 200/206. The unencoded field also needs the same effective decode chain or direct proof of the decoded bytes.
generates a 304, HEAD, or 206The actual outgoing content for Content-Digest. For multipart 206, include the serialized multipart body, boundaries, and part fields.A stored GET’s non-empty content digest belongs on an empty response, or a whole-representation digest necessarily equals a message-content digest.
transforms content codingNew message bytes, new coded representation data, and complete decoded data separately.An upstream strong ETag automatically proves a digest for the transformed stored bytes. If provenance is unavailable, the proposal’s strong-tag witness is unavailable.

A practical reader rule

For every digest member to be kept, installed, or emitted, ask: what exact bytes does this field cover now? If an allowed association witness is unavailable, the proposal is to recalculate over the resulting bytes or omit/remove the member. An unsupported algorithm may pass through only while its association is preserved; it cannot be recalculated when that association is lost.

Association is not validation of the original digest and is not authentication. The source review calculated no digest values.

Status and limits

As checked 9 Nov 2026, the cache-integrity document was active -00 with Datatracker state I-D Exists; it had no RFC stream or intended-status metadata. The separate Unencoded-Digest definition was revision -05, an active HTTP Working Group Internet-Draft in the RFC Editor queue, awaiting first editor. Both are work in progress and may change. This standards and draft-text review is not evidence of behavior in a deployed cache, browser, provider, or endpoint; it makes no claim about digest correctness, authenticity, or demand.

Read the dated report for the operation-by-operation rules, source status, and section links →

Search published pools, pages, reports, and evidence.