Dated report · cache integrity fields · 9 Nov 2026
Keeping HTTP digest fields attached to the bytes they describe
A source review of Content-Digest, Repr-Digest, and Unencoded-Digest through cache field updates, freshening, range combination, generated responses, and content-coding transformations.
Main finding
RFC 9111 defines general stored-field update, 304/HEAD freshening, and partial-response rules. RFC 9530 defines the byte inputs for Content-Digest and Repr-Digest. A separate, non-adopted cache-integrity Internet-Draft proposes a field-specific safeguard: for every digest dictionary member a cache would retain, install, or emit, keep the association with its defined input by an allowed witness, recalculate it over the resulting input, or remove it. A cache need not support or validate an algorithm if it removes a member it cannot safely carry through an input change. Association does not establish that the original digest was correct or authenticate the content.
The draft would constrain digest-member handling after RFC 9111 determines which stored response is relevant. It does not replace current RFC 9111 requirements or change the stored-response selection rules covered by the 304 response-selection guide.
First identify the exact input
| Field | Defined input | Consequence for cache operations |
|---|---|---|
Content-Digest | Exact HTTP message content bytes (RFC 9530 §2). | May describe a range, multipart serialization, or empty content. It is not inherently a whole-resource digest. |
Repr-Digest | Entire selected representation data (RFC 9530 §3); representation data are in coded form when a content coding is applied (RFC 9110 §8.1). | Can describe a complete representation even when this message contains only a range or no content. |
Unencoded-Digest | Entire selected representation data after all content codings are removed (draft-ietf-httpbis-unencoded-digest-05 §3). | With no content coding, its input is the same as Repr-Digest for the same algorithm; the definition remains WIP at this review date. |
Synthetic byte illustration only—not a test or digest calculation: let decoded bytes be abcdef and coded representation bytes be G. A full coded GET has content G; Content-Digest and Repr-Digest use G, while Unencoded-Digest uses abcdef. If a 206 carries the first three coded bytes, Content-Digest covers those three bytes, while the representation-level fields still refer to the full selected representation. A HEAD or 304 has no content, so its Content-Digest input is empty; representation-level fields may still describe the selected representation. This example shows input classes only: it does not claim that every message should include every field. RFC 9110 §14.1.2 measures ranges over the coded byte sequence when a content coding is applied.
What the published RFCs require today
| Operation | Current published rule | Digest-specific limit |
|---|---|---|
| Stored-field updates | RFC 9111 §3.2 generally requires adding each field from an updating response to the stored response, replacing existing values subject to its listed exceptions. A field is not omitted merely because its name begins with Content-. | This generic rule does not state the cache-integrity draft’s separate input-association test for digest members. |
| 304 freshening | RFC 9111 §4.3.4 determines suitable stored responses and applies §3.2 to update them. RFC 9110 §15.4.5 says a 304 ends at the header section and cannot contain content or trailers. | The stored-response candidates still come from RFC 9111. The separate issue here is which digest inputs remain associated after the selected response’s metadata is updated. |
| HEAD freshening | RFC 9111 §4.3.5 says a successful HEAD can update or invalidate stored GET responses and specifies conditions for applying §3.2. RFC 9110 §9.3.2 defines HEAD as having no content while its representation metadata describes a corresponding GET. | Current validator and (when supplied) Content-Length checks for HEAD freshening do not by themselves establish the digest-specific witness proposed for installing a new whole-representation digest member. |
| Partial response storage and combination | RFC 9111 §§3.3–3.4 permit storage/completion of supported partial responses and combination of ranges sharing a strong validator, subject to client requirements. RFC 9110 §15.3.7 defines 206 as conveying part(s) of a selected representation. | Neither the same-validator condition nor a digest on one range makes that message-content digest a digest over the combined content. |
These current RFC rules and the proposal below have different status. The cache-integrity draft does not change which response RFC 9111 selects for a 304 update, or the conditions under which a HEAD response updates or invalidates a stored GET.
What the cache-integrity draft proposes
Work in progress · not an adopted RFC
The proposal applies ordinary RFC 9111 update precedence first, then treats covered dictionary members independently. If an update omits a covered field, ordinary field-update rules decide whether its old value remains. If the update contains the field, the new parsed algorithm-key set replaces the old set: an omitted key is withdrawn and is not restored from the old field as a fallback. For every resulting member, the cache would preserve association with the applicable input, recalculate over the resulting input, or remove the member. If none remain, remove the field. A member using an unsupported algorithm can pass through only while its input association remains; it cannot be recalculated if association is lost. Conflicting values for the same key are recalculated or removed rather than resolved by choosing the newest; distinct keys are independent.
Content-Digest · message content
- An old member may remain only if ordinary update rules retain it and it is still associated with the exact retained content.
- An incoming member may be installed when incoming and retained content are the same octets, or the cache recalculates/validates it over the retained content; otherwise remove it.
- A 304 or HEAD digest for empty content cannot replace a member for non-empty retained GET content. If a present updater field replaces the key set, do not silently fall back to an old member that was withdrawn.
Repr-Digest · complete coded representation
- A member can be retained when complete representation data are directly established, or when the source and result have the same eligible strong entity tag in the same representation-selection context and cache operation.
- A weak tag,
Last-Modified,Content-Length, or validator-free freshening is not sufficient to install a new member. - If the update supplies the field but it cannot be associated with the retained representation, recalculate it there or remove it; absence of an updating field follows ordinary RFC 9111 retention rules.
Unencoded-Digest · complete decoded representation
The same complete-representation witness as Repr-Digest is required and the effective ordered content-decoding configuration must be unchanged, unless the cache directly establishes identical decoded bytes. A shared strong tag alone is insufficient. The proposal also requires considering decoding inputs beyond the Content-Encoding token list when a coding defines them.
Apply the distinction at each operation
| Cache operation | Proposal’s digest-specific treatment | Reader check |
|---|---|---|
| 304 or HEAD freshening | Apply digest rules separately to each stored response that RFC 9111 selects or updates. Do not copy the bodyless message’s Content-Digest onto retained GET bytes. Whole-representation fields need their own association evidence. | First determine the stored-response candidate/update path under RFC 9111; then ask what input each digest member still describes. Last-Modified or Content-Length may support an RFC 9111 HEAD path without becoming a digest witness. |
| Partial-response combination | The shared strong-validator condition remains necessary, but not enough for every field. Recalculate Content-Digest on the combined body or remove it. Repr-Digest can remain with an eligible strong-validator witness; Unencoded-Digest additionally needs the same effective decoding chain or direct decoded-data proof. | Do not copy a digest over one range onto the completed 200 or larger 206 as if it covered the new message content. |
| Cache-generated 304 or HEAD | Do not copy a stored GET’s non-empty Content-Digest onto the bodyless response. Omit it or calculate it for empty content. A representation-level member can be emitted only if its relevant association still applies; the proposal does not require adding optional fields. | Distinguish message content from the representation metadata described by HEAD or 304. |
| Cache-generated 206 | Content-Digest must describe the exact content sent or be removed. For multipart output, that includes the multipart serialization, boundaries, and part fields. Whole-representation fields can remain only while their complete-representation associations hold. | A single-range input and a multipart message body are different byte sequences. |
| Content-coding transformation | If outgoing message content changes, recalculate Content-Digest or remove it. If complete coded representation data change, recalculate Repr-Digest or remove it. Keep Unencoded-Digest only if the complete decoded representation is established unchanged; otherwise recalculate or remove it. | An upstream strong entity tag does not itself become a later Repr-Digest witness for transformed stored bytes. If transformation provenance is unavailable, the draft’s strong-tag witness is unavailable. |
The proposal does not change HTTP’s existing transformation controls, including Cache-Control: no-transform. Its scope is keeping digest members associated with the resulting inputs, not deciding whether a transformation is allowed.
Practical takeaway
Think in three scopes: this message, the complete coded representation, and the complete decoded representation. A validator or “same resource” intuition is not interchangeable across them. Under the proposed handling rules, preserve a member only with the applicable association evidence; otherwise recalculate over the bytes that will actually be represented or omit/remove the member. In particular, do not attach an empty-body digest from a 304/HEAD to retained GET content, or a one-range digest to a combined/generated response.
Draft status and evidence limits
draft-jurkovikj-http-integrity-cache-00is an initial individual Internet-Draft. Datatracker showed an active draft, no RFC stream or intended-status metadata, IESG stateI-D Exists, and only version -00 (uploaded 20 Aug 2026) in its history. The cover says “Intended status: Standards Track” and “Updates: 9111 (if approved)”; those words do not make it an adopted RFC. Its listed expiry is 21 Feb 2027, and its boilerplate says it is not endorsed and has no formal standing in the IETF standards process.draft-ietf-httpbis-unencoded-digest-05is also WIP. Datatracker showed -05 as an active HTTP Working Group Internet-Draft with IESG stateRFC Ed Queueand RFC Editor status “Awaiting First editor”; it was not a published RFC in the source reviewed. Its listed expiry is 19 Dec 2026. This report uses §3 only to identify the defined input forUnencoded-Digest.- Confidence is high for the cited RFC semantics and for what the draft text says; moderate for the operational synthesis across operations. Examples are synthetic and show input scopes only. No digest was calculated and no endpoint, browser, cache, provider, or implementation was tested.
- This report does not establish digest correctness or authenticity, cryptographic security, signature behavior, deployment behavior, or population demand. It does not cover digest algorithm internals or HTTP Message Signatures. Draft text can change or expire.
Sources and sections
- RFC 9110 — HTTP Semantics, §§8.1, 8.4, 9.3.2, 14.1.2, 15.3.7, 15.4.5: representation data and coding; HEAD/304 content; range units and 206.
- RFC 9111 — HTTP Caching, §§3.1–3.4, 4.3.4–4.3.5: stored fields and updates, partial responses, 304 update, HEAD freshening.
- RFC 9530 — Digest Fields, §§2–3 and Appendix B.1–B.5: definitions and examples for
Content-DigestandRepr-Digest. - draft-jurkovikj-http-integrity-cache-00, §§1.1, 3–10, 12, 16–17; Datatracker status and history: proposed cache association rules and version/status checked 9 Nov 2026.
- draft-ietf-httpbis-unencoded-digest-05, §3 only, and Datatracker status: work-in-progress definition and status checked 9 Nov 2026.