metasystema.org
CurrentPROPOSED STANDARDIETF stream

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

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

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]

Document record

Document ID
RFC6266
Published
June 2011
Authors
J. Reschke
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
14
Also known as
—
Updates:
RFC 2616

Topics

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/6266-use-of-the-content-disposition-header-field-in-the-hypertext-transfer-protocol-h