metasystema.org
ObsoletedPROPOSED STANDARDLegacy stream

RFC 3230: Instance Digests in HTTP

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9530.

Current version: RFC 9530 — Digest Fields

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

HTTP/1.1 defines a Content-MD5 header that allows a server to include a digest of the response body. However, this is specifically defined to cover the body of the actual message, not the contents of the full file (which might be quite different, if the response is a Content-Range, or uses a delta encoding). Also, the Content-MD5 is limited to one specific digest algorithm; other algorithms, such as SHA-1 (Secure Hash Standard), may be more appropriate in some circumstances. Finally, HTTP/1.1 provides no explicit mechanism by which a client may request a digest. This document proposes HTTP extensions that solve these problems. [STANDARDS-TRACK]

Document record

Document ID
RFC3230
Published
January 2002
Authors
J. Mogul; A. Van Hoff
Status
PROPOSED STANDARD
Stream
Legacy
Area
—
Pages
13
Also known as
—
Obsoleted by:
RFC 9530

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

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

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/3230-instance-digests-in-http