Content-Digest
An HTTP field, defined in RFC 9530, that carries a hash of the message body, such as sha-256, so the receiver can confirm the bytes were not changed in transit. Signed requests under HTTP Message Signatures commonly include it, which binds the signature to the body.
What Content-Digest does not show
It proves the body matches the digest; it says nothing about whether the content is true.
Terms this definition uses
SHA-256 · HTTP Message Signatures
Related terms in HTTP, edge and rendering
The delivery layer between an origin and a client: proxies, caches, redirects, status codes and the headers that decide what a crawler actually received.
Link header · content negotiation · Markdown negotiation · Retry-After · Server-Timing · WWW-Authenticate · Allow header · Origin server · Reverse proxy · CDN · Edge node · WAF · Bot score · TLS handshake · DNS resolution · DNS timeout · Connection timeout · Read timeout · Redirect chain · Redirect loop · 301 redirect · 302 redirect · 307 redirect · 308 redirect · 304 response · 404 response · 410 response · 429 response · 500 response · 502 response · 503 response · 504 response · HEAD request · GET request · Content type · MIME sniffing · Content encoding · Compression · Brotli · ETag · Last-Modified · If-None-Match · Cache hit · Cache miss · Cache key · Vary header · Stale response · Stale-while-revalidate · Edge redirect · Origin bypass · Response parity · Header parity · hreflang · canonical URL · HSTS · HSTS preload list · Content-Security-Policy · CSP nonce · edge cache · cache split · cache-buster · Cache-Control · Age header · render-blocking resource · payload text share · lazy loading · 404 and 410 status codes
Questions about Content-Digest
What is Content-Digest?
An HTTP field, defined in RFC 9530, that carries a hash of the message body, such as sha-256, so the receiver can confirm the bytes were not changed in transit. Signed requests under HTTP Message Signatures commonly include it, which binds the signature to the body.
What does Content-Digest not show or guarantee?
An HTTP field, defined in RFC 9530, that carries a hash of the message body, such as sha-256, so the receiver can confirm the bytes were not changed in transit. It proves the body matches the digest; it says nothing about whether the content is true.
Which area of the glossary does Content-Digest belong to?
HTTP, edge and rendering: The delivery layer between an origin and a client: proxies, caches, redirects, status codes and the headers that decide what a crawler actually received.
← Allow header · Origin server →
See it in the full glossary · 751 terms across 19 areas.