Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol
RFC 6266, “Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol”, is a Proposed Standard document published in June 2011 by J. Reschke. It updates RFC 2616. The canonical text is published by the RFC Editor.
Abstract
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 definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6266 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6265 HTTP State Management Mechanism
- RFC 6267 MIKEY-IBAKE: Identity-Based Authenticated Key Exchange Mode of Key Distribution in Multimedia Internet KEYing
- RFC 6264 An Incremental Carrier-Grade NAT for IPv6 Transition
- RFC 6268 Additional New ASN.1 Modules for the Cryptographic Message Syntax and the Public Key Infrastructure Using X.509
- RFC 6263 Application Mechanism for Keeping Alive the NAT Mappings Associated with RTP / RTP Control Protocol Flows
- RFC 6269 Issues with IP Address Sharing
- RFC 6262 RTP Payload Format for IP-MR Speech Codec
- RFC 6270 The 'tn3270' URI Scheme