RFC 1864: The Content-MD5 Header Field
In plain English — editorial summary, not part of the RFC
This memo specifies an optional header field, Content-MD5, for use with MIME-conformant messages. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1864
- Published
- October 1995
- Authors
- J. Myers; M. Rose
- Status
- DRAFT STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 4
- Also known as
- —
- Obsoletes:
- RFC 1544
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1806Communicating Presentation Information in Internet Messages: The Content-Disposition HeaderObsoleted
June 1995
- RFC 2183Communicating Presentation Information in Internet Messages: The Content-Disposition Header FieldUpdated
August 1997
- RFC 1524A User Agent Configuration Mechanism For Multimedia Mail Format InformationCurrent
September 1993
- RFC 5068Email Submission Operations: Access and Accountability RequirementsUpdated
November 2007
- RFC 5403RPCSEC_GSS Version 2Updated
February 2009
- RFC 5598Internet Mail ArchitectureCurrent
July 2009
- RFC 6376DomainKeys Identified Mail (DKIM) SignaturesUpdated
September 2011
- RFC 6377DomainKeys Identified Mail (DKIM) and Mailing ListsCurrent
September 2011
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?