msg
1.12.11devel
|
This submodule contains the header classes, functions and types for handling MIME headers (RFC 2045) and MIME multipart (RFC 2046) processing. More...
Modules | |
MIME Multipart Body | |
Representing MIME multipart bodies and their manipulation. | |
Accept Header | |
The Accept request-header field can be used to specify certain media types which are acceptable for the response. Its syntax is defined in [H14.1, S20.1] as follows: | |
Accept-Charset Header | |
The Accept-Charset header is similar to Accept, but restricts the character set that are acceptable in the response. Its syntax is defined in [H14.2] as follows: | |
Accept-Encoding Header | |
The Accept-Encoding header is similar to Accept, but restricts the content-codings that are acceptable in the response. Its syntax is defined in [H14.3, S20.2] as follows: | |
Accept-Language Header | |
The Accept-Language header allows the client to indicate to the server in which language it would prefer to receive reason phrases, session descriptions or status responses carried as message bodies. Its syntax is defined in [H14.4, S20.3] as follows: | |
Content-Disposition Header | |
The Content-Disposition header field describes how the message body or, in the case of multipart messages, a message body part is to be interpreted by the UAC or UAS. Its syntax is defined in [S20.11] as follows: | |
Content-Encoding Header | |
The Content-Encoding header indicates what additional content codings have been applied to the entity-body. Its syntax is defined in [H14.11] and [S20.12] as follows: | |
Content-Language Header | |
The Content-Language header describes the natural language(s) of the intended audience for the enclosed message body. Note that this might not be equivalent to all the languages used within the message-body. Its syntax is defined in [H14.12, S20.13] as follows: | |
Content-Length Header | |
The Content-Length header indicates the size of the message-body in decimal number of octets. Its syntax is defined in [S10.18] as follows: | |
Content-MD5 Header | |
The Content-MD5 header is an MD5 digest of the entity-body for the purpose of providing an end-to-end message integrity check (MIC) of the message-body. Its syntax is defined in [RFC 1864, H14.15] as follows: | |
Content-ID Header | |
The Content-ID header is an unique identifier of an entity-body. The Content-ID value may be used for uniquely identifying MIME entities in several contexts, particularly for caching data referenced by the message/external-body mechanism. Its syntax is defined in [RFC2045] as follows: | |
Content-Type Header | |
The Content-Type header indicates the media type of the message-body sent to the recipient. Its syntax is defined in [H3.7, S20.15] as follows: | |
MIME-Version Header | |
MIME-Version header indicates what version of the protocol was used to construct the message. Its syntax is defined in [H19.4.1, S20.24] as follows: | |
Content-Location Header | |
Content-Transfer-Encoding Header | |
Warning Header | |
The Warning response-header field is used to carry additional information about the status of a response. Its syntax is defined in [S20.43] as follows: | |
Files | |
file | msg_mime.h |
file | msg_mime_protos.h |
This submodule contains the header classes, functions and types for handling MIME headers (RFC 2045) and MIME multipart (RFC 2046) processing.
The MIME headers implemented are as follows: