metasystema.org
UpdatedPROPOSED STANDARDLegacy stream

RFC 2183: Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field

Still current, but amended. Parts of this document are changed or extended by RFC 2184, RFC 2231. Read both.

In plain English — editorial summary, not part of the RFC

This memo provides a mechanism whereby messages conforming to the MIME specifications [RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049] can convey presentational information. It specifies the "Content- Disposition" header field, which is optional and valid for any MIME entity ("message" or "body part"). [STANDARDS-TRACK]

Document record

Document ID
RFC2183
Published
August 1997
Authors
R. Troost; S. Dorner; K. Moore
Status
PROPOSED STANDARD
Stream
Legacy
Area
—
Pages
12
Also known as
—
Obsoletes:
RFC 1806
Updated by:
RFC 2184, RFC 2231

Topics

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/2183-communicating-presentation-information-in-internet-messages-the-content-disposit