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

This memo provides a mechanism whereby messages conforming to the MIME specifications [RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049] can convey…

Read RFC 2183 on the RFC Editor

Outgoing relationships (10 related RFCs)

Obsoletes, Informative reference — RFC 1806: Communicating Presentation Information in Internet Messages: The Content-Disposition Header
Informative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Informative reference — RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
Informative reference — RFC 822: STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
Informative reference — RFC 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
Informative reference — RFC 2047: MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
Informative reference — RFC 1521: MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies
Informative reference — RFC 2048: Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
Informative reference — RFC 2049: Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples
Informative reference — RFC 2184: MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations

Incoming relationships (27 related RFCs)

Updated by, Informatively referenced by — RFC 2231: MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
Updated by — RFC 2184: MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
Normatively referenced by — RFC 3261: SIP: Session Initiation Protocol
Normatively referenced by — RFC 3851: Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification
Normatively referenced by — RFC 5751: Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification
Normatively referenced by — RFC 4975: The Message Session Relay Protocol (MSRP)
Normatively referenced by — RFC 3801: Voice Profile for Internet Mail - version 2 (VPIMv2)
Normatively referenced by — RFC 9051: Internet Message Access Protocol (IMAP) - Version 4rev2
Normatively referenced by — RFC 3459: Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter
Normatively referenced by — RFC 3923: End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP)
Normatively referenced by — RFC 5536: Netnews Article Format
Normatively referenced by — RFC 5547: A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer
Normatively referenced by — RFC 6857: Post-Delivery Message Downgrading for Internationalized Email Messages
Normatively referenced by — RFC 5363: Framework and Security Considerations for Session Initiation Protocol (SIP) URI-List Services
Normatively referenced by — RFC 5621: Message Body Handling in the Session Initiation Protocol (SIP)
Normatively referenced by — RFC 5825: Displaying Downgraded Messages for Email Address Internationalization
Normatively referenced by — RFC 7578: Returning Values from Forms: multipart/form-data
Normatively referenced by — RFC 7763: The text/markdown Media Type
Normatively referenced by — RFC 8255: Multiple Language Content Type
Normatively referenced by — RFC 9078: Reaction: Indicating Summary Reaction to a Message
Informatively referenced by — RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
Informatively referenced by — RFC 2311: S/MIME Version 2 Message Specification
Informatively referenced by — RFC 2421: Voice Profile for Internet Mail - version 2
Informatively referenced by — RFC 3458: Message Context for Internet Mail
Informatively referenced by — RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)
Informatively referenced by — RFC 2626: The Internet and the Millennium Problem (Year 2000)
Informatively referenced by — RFC 4263: Media Subtype Registration for Media Type text/troff