Content Disposition Values and Parameters Last Updated 2021-09-14 Note In [ RFC2183 ] there is a discussion of the "Content-Disposition" header field and the description of the initial values allowed in this header. Additional values may be registered with the IANA following the …

…features defined in the Multipurpose Internet Mail Extensions (MIME) variant ( [RFC2183] ) of the header field, and also clarifies internationalization aspects. Note: This document does not apply to Content-Disposition header fields appearing in payload bodies transmitted over HT…

… features defined in the Multipurpose Internet Mail Extensions (MIME) variant ([RFC2183]) of the header field, and also clarifies internationalization aspects. Reschke Standards Track [Page 2] RFC 6266 Content-Disposition in HTTP June 2011 Note: This document does not apply to Co…

…features defined in the Multipurpose Internet Mail Extensions (MIME) variant ([ RFC2183 ]) of the header field, and also clarifies internationalization aspects. Reschke Standards Track [Page 2] RFC 6266 Content-Disposition in HTTP June 2011 Note: This document does not apply to C…

…Field for Each Part Each part MUST contain a Content-Disposition header field [ RFC2183 where the disposition type is "form-data". The Content-Disposition header field MUST also contain an additional parameter of "name"; the value of the "name" parameter is the original field nam…

…stems. Sending agents SHOULD also emit the optional Content-Disposition field [ RFC2183 ] with the "filename" parameter. If a sending agent emits the above parameters, the value of the parameters SHOULD be a filename with the appropriate extension: File Media Type Extension -----…

…C4952] or in [RFC5321], [RFC5322], or the MIME documents [RFC2045], [RFC2047], [RFC2183], and [RFC2231]. This document depends on [RFC5335] and [RFC5504]. Key words used in those documents are used in this document, too. The term "MIME decode" is used for both "encoded-word" deco…

…ecifications [RFC5321] [RFC5322], or in the MIME documents [RFC2045] [RFC2047] [RFC2183] [RFC2231]. The terms "ASCII address", "internationalized email address", "non-ASCII address", "i18mail address", "UTF8SMTP", "message", and "mailing list" are used with the definitions from […

…tions [ RFC5321 ] [ RFC5322 ], or in the MIME documents RFC2045 ] [ RFC2047 ] [ RFC2183 ] [ RFC2231 ]. The terms "ASCII address", "internationalized email address", "non-ASCII address", "i18mail address", "UTF8SMTP", "message", and "mailing list" are used with the definitions fro…

…or in [ RFC5321 ], [ RFC5322 ], or the MIME documents RFC2045 ], [ RFC2047 ], [ RFC2183 ], and [ RFC2231 ]. This document depends on [ RFC5335 ] and [ RFC5504 ]. Key words used in those documents are used in this document, too. The term "MIME decode" is used for both "encoded-wor…

…tted. This parameter provides mostly indicative information. The suggestions in RFC2183 apply: Prefer ASCII characters if possible (the client may percent-encode it, as long as the server implementation decodes it). Any path information should be stripped, such as by replacing / …

…Content-Description are defined in RFC2045. ; Content-Disposition is defined in RFC2183 ; MIME-extension-field indicates additional MIME extension ; header fields as described in RFC2045 data = *OCTET end-line = "-------" transact-id continuation-flag CRLF continuation-flag = "+"…

…rifier Name: Barry Leiba Date Verified: 2013-02-03 In Appendix B: Section 2 of [RFC2183] defines several additional disposition parameters: "creation-date", "modification-date", "quoted-date-time", and "size". It should say: Section 2 of [RFC2183] defines several additional dispo…

…han 2000000000 (fairly clearly 502(continued): ), and 503: 504: +=+=+=+=+= File rfc2183 .txt +=+=+=+=+= century found at line 8: 6: 7: Network Working Group R 7(continued): . Troost 8: Request for Comments: 2183 New Century 8(continued): Systems 9: Updates: 1806 S 9(continued): .…

…rifier Name: Barry Leiba Date Verified: 2013-02-03 In Appendix B: Section 2 of [RFC2183] defines several additional disposition parameters: "creation-date", "modification-date", "quoted-date-time", and "size". It should say: Section 2 of [RFC2183] defines several additional dispo…