Topic Path: Symbol Reference > Classes > TIdAttachment Class > TIdAttachment Properties > ContentDisposition Property
ContentsIndexHome
PreviousUpNext
TIdAttachment.ContentDisposition Property

Indicates presentation and storage parameters for the message part.

property ContentDisposition: string;

ContentDisposition is a String property that represents the value for the Internet Message header "Content-Disposition", as described in the Intenet Standards documents: 

RFC 2183 - Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field  

ContentDisposition indicates presentation information for the message part and can contain values and optional parameters. 

ContentDisposition can include the following values and associated meanings, as described in the indicated Internet Standards document: 

 

Value 
Description 
RFC 
inline 
displayed automatically 
RFC 2183 
attachment 
user controlled display 
RFC 2183 
form-data 
process as form response 
RFC 2388 
signal 
tunneled content is processed silently 
RFC 3204 
alert 
body is a ring tone to alert the user 
RFC 3261 
icon 
body displayed as an icon to the user 
RFC 3261 
render 
body should be displayed to the user 
RFC 3261 
session 
body describes a communications session 
RFC 3261 
signed-receipt-protocol 
requested signature format for receipt 
RFC 3335 
signed-receipt-micalg 
requested signature algorithm for receipt 
RFC 3335 

 

The values "inline" and "attachment" are the most commonly used ContentDisposition values for attachements. 

"inline" indicates the message part should be display immediately, and in the order in which it occurs. 

"attachment" indicates that the message part is separate from the main body of the message, and suggests a file where the message part may be stored. 

ContentDisposition may contain optional parameters in "attribute=value" form, that includes the following parameters names and associated meanings: 

 

Parameter 
Meaning 
RFC 
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 2388 
voice 
type or use of audio content 
RFC 2421 
handling 
wheter or not processing is required 
RFC 3204 

 

Some content disposition parameters have specific values which must be used, as described in the following: 

 

Parameter 
Value 
RFC 
voice 
Voice-Message 
RFC 2421 
voice 
Voice-Message-Notification 
RFC 2421 
voice 
Originator-Spoken-Name 
RFC 2421 
voice 
Recipient-Spoken-Name 
RFC 2421 
voice 
Spoken-Subject 
RFC 2421 
handling 
required 
RFC 3204 
handling 
optional 
RFC 3204 

 

When ContentDisposition contains "attachment", the FileName property reflects the file where the message part is stored. Other parameters names and values are left in the ContentDisposition property. 

For more detailed information about ContentDisposition values, please refer to the following: 

RFC 2183 - Communicating Presentation Information in Internet Messages: The Content - Disposition Header Field  

RFC 2388 - Returning Values from Forms: multipart/form-data  

RFC 2421 - Voice Profile for Internet Mail (version 2)  

RFC 3204 - MIME media types for ISUP and QSIG Objects  

RFC 3261 - SIP: Session Initiation Protocol  

RFC 3335 - MIME-based Secure Peer-to-Peer Business Data Interchange over the Internet  

Copyright 1993-2006, Chad Z. Hower (aka Kudzu) and the Indy Pit Crew. All rights reserved.
Post feedback to the Indy Docs Newsgroup.