Digest Fields
RFC 9530
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['Digest']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "L. Pardue": changed name from "Lucas Pardue" to "L. Pardue" |
|
2026-05-20
|
(System) | Changed author "R. Polli": changed name from "Roberto Polli" to "R. Polli", changed affiliation from "Team Digitale, Italian Government" to "Team Digitale Italian Government", cleared … Changed author "R. Polli": changed name from "Roberto Polli" to "R. Polli", changed affiliation from "Team Digitale, Italian Government" to "Team Digitale Italian Government", cleared country (was "Italy") |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2024-10-29
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2024-10-24
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2024-02-16
|
(System) | IANA registries were updated to include RFC9530 |
|
2024-02-14
|
(System) | Received changes through RFC Editor sync (created document RFC 9530, created became rfc relationship between draft-ietf-httpbis-digest-headers and RFC 9530, set abstract to 'This … Received changes through RFC Editor sync (created document RFC 9530, created became rfc relationship between draft-ietf-httpbis-digest-headers and RFC 9530, set abstract to '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.', set pages to 32, set standardization level to Proposed Standard, added RFC published event at 2024-02-14, created obsoletes relation between RFC 9530 and RFC 3230) |
|
2024-02-14
|
(System) | RFC published |