msg  1.12.11devel
Modules
Here is a list of all modules:
[detail level 12]
 Parser Building BlocksThis submodule contains the functions and types for building a protocol-specific parser
 HeadersThis submodule contains the functions and types for handling message headers and other elements
 Erroneous HeadersThe erroneous headers are stored in msg_error_t structure
 Unknown HeadersThe unknown headers are handled with msg_unknown_t structure. The whole unknown header including its name is included in the header value string g_value
 Message BodyThe payload object contains the message body. The message body has no structure, but it is stored in the pl_data buffer as a byte array. Multiple payload objects may be linked to a list
 Message SeparatorAn empty line separates headers from the message body. In order to avoid modifying messages with integrity protection, the separator line has its own header structure which is included in the msg_t structure
 MIME HeadersThis submodule contains the header classes, functions and types for handling MIME headers (RFC 2045) and MIME multipart (RFC 2046) processing
 MIME Multipart BodyRepresenting MIME multipart bodies and their manipulation
 Accept HeaderThe 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 HeaderThe 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 HeaderThe 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 HeaderThe 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 HeaderThe 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 HeaderThe 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 HeaderThe 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 HeaderThe 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 HeaderThe 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 HeaderThe 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 HeaderThe 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 HeaderMIME-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 HeaderThe 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:
 Testing ParserThis submodule contains the functions and types for building a parser objects for testing purposes

Sofia-SIP 1.12.11devel - Copyright (C) 2006 Nokia Corporation. All rights reserved. Licensed under the terms of the GNU Lesser General Public License.