Content Disposition Values and Parameters
In RFC 2183 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 procedures in Section 9 of RFC 2183.
Content Disposition Values
- Standards Track or IESG-Approved Experimental RFC
- RFC 2183: Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field
| Value |
Description |
Allowed Values |
Reference |
| inline |
displayed automatically |
(none) |
RFC 2183 |
| attachment |
user controlled display |
filename, creation-date, modification-date, read-date, size, handling |
RFC 2183 |
| form-data |
process as form response |
name, filename |
RFC 7578 |
| signal |
tunneled content to be processed silently |
handling |
RFC 3204 |
| alert |
the body is a custom ring tone to alert the
user |
handling |
RFC 3261 |
| icon |
the body is displayed as an icon to the user |
handling |
RFC 3261 |
| render |
the body should be displayed to the user |
handling |
RFC 3261 |
| recipient-list-history |
the body contains a list of URIs that
indicates the recipients of the request |
handling |
RFC 5364 |
| session |
the body describes a communications session,
for example, an RFC2327 SDP body |
handling |
RFC 3261 |
| aib |
Authenticated Identity Body |
handling |
RFC 3893 |
| early-session |
the body describes an early communications
session, for example, and [RFC2327] SDP body |
(none) |
RFC 3959 |
| recipient-list |
The body includes a list of URIs to which
URI-list services are to be applied. |
(none) |
RFC 5363 |
| notification |
the payload of the message carrying this
Content-Disposition header field value is
an Instant Message Disposition Notification
as requested in the corresponding Instant
Message. |
(none) |
RFC 5438 |
| by-reference |
The body needs to be handled according to a
reference to the body that is located in
the same SIP message as the body. |
handling |
RFC 5621 |
| info-package |
The body contains information associated with an
Info Package |
(none) |
RFC 6086 |
| recording-session |
The body describes either metadata about the RS or the reason
for the metadata snapshot request as determined by the MIME
value indicated in the Content-Type. |
(none) |
RFC 7866 |
Content Disposition Parameters
- RFC 2183: Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field
| Name |
Description |
Reference |
| filename |
name to be used when creating file |
RFC 2183 |
| creation-date |
date when content was created |
RFC 2183 |
| modification-date |
date when content was last modified |
RFC 2183 |
| read-date |
date when content was last read |
RFC 2183 |
| size |
approximate size of content in octets |
RFC 2183 |
| name |
original field name in form |
RFC 7578 |
| voice |
type or use of audio content |
RFC 2421 |
| handling |
whether or not processing is required |
RFC 3204 |
| preview-type |
Internet media type (and parameters) of the preview output desired from a processor by the author of the MIME content |
RFC 7763 |
| reaction |
Permit a recipient to respond by signaling basic
reactions to an author's posting, such as with a 'thumbs up' or
'smiley' graphic |
RFC 9078 |
Voice Parameter Values
- RFC 2421: Voice Profile for Internet Mail - version 2
Handling Parameter Values
- RFC 3204: MIME media types for ISUP and QSIG Objects
| Value |
Description |
Reference |
| required |
body must be understood |
RFC 3204 |
| optional |
body may be silently discarded |
RFC 3204 |
