RFC 6266: Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)

RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the…

Read RFC 6266 on the RFC Editor

Outgoing relationships (10 related RFCs)

Updates, Normative reference — RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5987: Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters
Informative reference — RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
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 3864: Registration Procedures for Message Header Fields
Informative reference — RFC 2183: Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field
Informative reference — RFC 2231: MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
Informative reference — RFC 2388: Returning Values from Forms: multipart/form-data

Incoming relationships (2 related RFCs)

Informatively referenced by — RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
Informatively referenced by — RFC 8187: Indicating Character Encoding and Language for HTTP Header Field Parameters