RFC 9530: Digest Fields

In plain English — editorial summary, not part of the RFC

This document defines HTTP fields that support integrity digests. The Content-Digest field can be used for the integrity of HTTP message content. The Repr-Digest field can be used for the integrity of HTTP representations. Want-Content-Digest and Want-Repr-Digest can be used to indicate a sender's interest and preferences for receiving the respective Integrity fields. This document obsoletes RFC 3230 and the Digest and Want-Digest HTTP fields.

Document record

Document ID

RFC9530

Published

February 2024

Authors

R. Polli; L. Pardue

Status

PROPOSED STANDARD

Stream

IETF

Area

wit

Pages

32

Also known as

—

Obsoletes:

RFC 3230

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC9530
• Reported errata exist →

Topics

• Digest

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 5925The TCP Authentication OptionCurrent

  June 2010

• RFC 7638JSON Web Key (JWK) ThumbprintCurrent

  September 2015

• RFC 4490Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with Cryptographic Message Syntax (CMS)Current

  May 2006

• RFC 4357Additional Cryptographic Algorithms for Use with GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 AlgorithmsCurrent

  January 2006

• RFC 2537RSA/MD5 KEYs and SIGs in the Domain Name System (DNS)Obsoleted

  March 1999

• RFC 2385Protection of BGP Sessions via the TCP MD5 Signature OptionObsoleted

  August 1998

• RFC 2104HMAC: Keyed-Hashing for Message AuthenticationUpdated

  February 1997

• RFC 2085HMAC-MD5 IP Authentication with Replay PreventionCurrent

  February 1997

Also filed under

• PROPOSED STANDARD
• 2024
• IETF stream
• wit area