The Content-MD5 Header Field, November 1993
- File formats:
- PROPOSED STANDARD
- Obsoleted by:
- RFC 1864
- M. Rose
- 822ext (app)
Discuss this RFC: Send questions or comments to email@example.com
This memo defines the use of an optional header field, Content-MD5, which may be used as a message integrity check (MIC), to verify that the decoded data are the same data that were initially sent. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.