RFC 2110 (rfc2110) - Page 2 of 19
MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)
Alternative Format: Original Text Document
RFC 2110 MHTML March 1997
8.1 General principle..................................... 11
8.2 Use of the Content-Location header.................... 11
8.3 Use of the Content-ID header and CID URLs............. 12
9 Examples................................................... 12
9.1 Example of a HTML body without included linked objects 12
9.2 Example with absolute URIs to an embedded GIF picture 13
9.3 Example with relative URIs to an embedded GIF picture 13
9.4 Example using CID URL and Content-ID header to an
embedded GIF picture.................................. 14
10. Content-Disposition header............................... 15
11. Character encoding issues and end-of-line issues......... 15
12. Security Considerations.................................. 16
13. Acknowledgments.......................................... 17
14. References............................................... 18
15. Author's Address......................................... 19
Mailing List Information
Further discussion on this document should be done through the
mailing list .
To subscribe to this list, send a message to
which contains the text
SUB MHTML
Archives of this list are available by anonymous ftp from
FTP://SEGATE.SUNET.SE/lists/mHTML/
The archives are also available by e-mail. Send a message to
with the text "INDEX MHTML" to get a list
of the archive files, and then a new message "GET " to
retrieve the archive files.
Comments on less important details may also be sent to the editor,
Jacob Palme [email protected]>.
More information may also be available at URL:
HTTP://www.dsv.su.se/~jpalme/ietf/jp-ietf-home.HTML
1. Introduction
There are a number of document formats, HTML [HTML2], PDF [PDF] and
VRML for example, which provide links using URIs for their
resolution. There is an obvious need to be able to send documents in
these formats in e-mail [RFC 821=SMTP, RFC 822]. This document gives
additional specifications on how to send such documents in MIME [RFC
1521=MIME1] e-mail messages. This version of this standard was based
on full consideration only of the needs for objects with links in the
Palme & Hopmann Standards Track