The Content-Digest HTTP header — integrity & signing, RFC 9530, declared by 1 providers in the API Evangelist catalog.
Content-Digest
Integrity & Signing IANA permanent response
A reference entry. The registry facts and catalog measurements below are complete; the written guidance for this header has not been authored yet.
Content-Digest is integrity & signing — Headers carrying a digest or a signature over the message, so a recipient can prove it arrived as it was sent.
The registry
Listed in the IANA HTTP Field Name Registry as a permanent entry. Defined in RFC 9530, Section 2: Digest Fields. It is a structured field of type Dictionary (RFC 9651).
In the catalog
Declared by 1 providers across 1 published specification files in the API Evangelist catalog, where it appears as a response header — sent by the server.
Governed by these rules
Machine-enforceable governance rules from rules.apievangelist.com that apply to this header when it appears in an OpenAPI.
OpenAPI Components Headers Error error
Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses
Guidance: Rate Limits →OpenAPI Components Headers Info info
Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses
Guidance: Rate Limits →OpenAPI Headers Hyphenated Pascal Case error
HTTP headers should follow Hyphenated-Pascal-Case naming convention for consistency and readability, such as Content-Type, X-Request-Id, or Accept-Language.
Guidance: Naming →