The Content-MD5-Origin: header
draft-hamilton-content-md5-origin-01

Document Type Expired Internet-Draft (individual)
Last updated 1999-03-02
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-hamilton-content-md5-origin-01.txt

Abstract

The Content-MD5: header specified in RFC 1864 has not been widely deployed, though this would be highly desirable for a number of reasons. The author conjectures that this lack of usage is due at least in part to the requirement that only originating user agents may add a Content-MD5: header. This proposal updates RFC 1864 to remove that requirement, and defines the header Content-MD5-Origin: for use by relaying hosts to indicate the point at which a Content- MD5: header was added.

Authors

Martin Hamilton (m.t.hamilton@lut.ac.uk)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)