Browse Prior Art Database

MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML) (RFC2110)

IP.com Disclosure Number: IPCOM000002663D
Original Publication Date: 1997-Mar-01
Included in the Prior Art Database: 2019-Feb-15
Document File: 19 page(s) / 26K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Palme: AUTHOR [+1]

Related Documents

10.17487/RFC2110: DOI

Abstract

This document describes a set of guidelines that will allow conforming mail user agents to be able to send, deliver and display these objects, such as HTML objects, that can contain links represented by URIs. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 8% of the total text.

Network Working Group J. Palme Request for Comments: 2110 Stockholm University/KTH Category: Standards Track A. Hopmann Microsoft Corporation March 1997

MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)

Status of this Document

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Abstract

Although HTML [RFC 1866] was designed within the context of MIME, more than the specification of HTML as defined in RFC 1866 is needed for two electronic mail user agents to be able to interoperate using HTML as a document format. These issues include the naming of objects that are normally referred to by URIs, and the means of aggregating objects that go together. This document describes a set of guidelines that will allow conforming mail user agents to be able to send, deliver and display these objects, such as HTML objects, that can contain links represented by URIs. In order to be able to handle inter-linked objects, the document uses the MIME type multipart/related and specifies the MIME content-headers "Content- Location" and "Content-Base".

Table of Contents

1. Introduction.............................................. 2 2. Terminology............................................... 3 2.1 Conformance requirement terminology................... 3 2.2 Other terminology..................................... 4 3. Overview.................................................. 5 4. The Content-Location and Content-Base MIME Content Headers 6 4.1 MIME content headers.................................. 6 4.2 The Content-Base header............................... 7 4.3 The Content-Location Header........................... 7 4.4 Encoding of URIs in e-mail headers.................... 8 5. Base URIs for resolution of relative URIs................. 8 6. Sending documents without linked objects.................. 9 7. Use of the Content-Type: Multipart/related................ 9 8. Format of Links to Other Body Parts....................... 11

Palme & Hopmann Standards Track [Page 1]

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....

Processing...
Loading...