Internet Assigned Numbers Authority • Domains • Protocols • Numbers • About Content Disposition Values and Parameters Last Updated 2021-09-14 Note 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]. Available Formats [IMG] XML [IMG] HTML [IMG] TXT Registries Included Below • Content Disposition Values • Content Disposition Parameters • Voice Parameter Values • Handling Parameter Values Content Disposition Values Registration Procedure(s) Standards Track or IESG-Approved Experimental RFC Reference [RFC 2183] Available Formats [IMG] CSV Value Description Allowed Values Reference inline displayed automatically (none) [RFC 2183] attachment user controlled display filename, creation-date, modification-date, [RFC 2183] read-date, size, handling 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 handling [RFC 5364] request session the body describes a communications session, for example, an RFC2327 SDP handling [RFC 3261] body aib Authenticated Identity Body handling [RFC 3893] early-session the body describes an early communications session, for example, and (none) [RFC 3959] [RFC2327] SDP body recipient-list The body includes a list of URIs to which URI-list services are to be (none) [RFC 5363] applied. the payload of the message carrying this Content-Disposition header notification field value is an Instant Message Disposition Notification as requested (none) [RFC 5438] in the corresponding Instant Message. by-reference The body needs to be handled according to a reference to the body that handling [RFC 5621] is located in the same SIP message as the body. info-package The body contains information associated with an Info Package (none) [RFC 6086] The body describes either metadata about the RS or the reason for the recording-session metadata snapshot request as determined by the MIME value indicated in (none) [RFC 7866] the Content-Type. Content Disposition Parameters Registration Procedure(s) First Come First Served Reference [RFC 2183] Available Formats [IMG] CSV 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' [RFC 9078] graphic Voice Parameter Values Registration Procedure(s) Not Defined Reference [RFC 2421] Available Formats [IMG] CSV Value Reference Voice-Message [RFC 2421] Voice-Message-Notification [RFC 2421] Originator-Spoken-Name [RFC 2421] Recipient-Spoken-Name [RFC 2421] Spoken-Subject [RFC 2421] Handling Parameter Values Registration Procedure(s) Not Defined Reference [RFC 3204] Available Formats [IMG] CSV Value Description Reference required body must be understood [RFC 3204] optional body may be silently discarded [RFC 3204] Licensing Terms