Applies to: Protocol and format interpretation for developers inspecting authorized media delivery.
The useful distinctions
- An entity tag identifies a selected representation version.
- The W/ prefix marks a weak entity tag.
- The specification does not prescribe an ETag generation algorithm.
Do not decode an identifier by appearance
An entity tag that resembles a hexadecimal digest is still an identifier supplied by the server. A client cannot safely infer its hash algorithm, file size, creation date, or security properties from its shape. For the invented tag in the example, all a diagnostic ledger needs is the exact quoted value and the resource selection context in which it appeared. Retaining case and punctuation avoids creating a different identifier during transcription.
Keep comparisons tied to their purpose
A report should state whether it is discussing reusable content, byte identity, or concurrency protection. Those tasks can require different comparison rules. Mixing them under a vague same-file label creates mistakes, especially when weak tags enter a workflow that manipulates byte offsets. The example deliberately uses a readable revision token instead of a hash-looking string: the operational discipline is the same. A later different token is evidence that the validator changed; it is not a description of what changed inside the media. Track byte counts and track metadata as separate observations if those details matter to the investigation. For revision review, compare complete strings and record equality as a result. Avoid slicing off punctuation or shortening the token in a machine-readable ledger merely because an abbreviated label looks cleaner.
Worked example · synthetic
The tag is quoted and has no weak prefix. The readable word rev is an author-chosen token in this synthetic response, not a standardized field inside the ETag value.
Synthetic text example; no network operation has been performed.
HTTP/MIME line endings are CRLF. Request URL context, where labelled, is commentary rather than a wire field. No message was transmitted.
HTTP/1.1 200 OK
Date: Sun, 08 Nov 2026 08:00:00 GMT
ETag: "documentary-rev-17"
Content-Length: 0
Check the interpretation
- Preserve the whole quoted tag.
- Do not treat it as a checksum unless the publisher documents that separately.
- Record the selected resource and negotiation inputs.