Connected: An Internet Encyclopedia
RFC 1945 - 3.6.2 Multipart Types

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1945
Up: 3. Protocol Parameters
Up: 3.6 Media Types
Prev: 3.6.1 Canonicalization and Text Defaults
Next: 3.7 Product Tokens

### 3.6.2 Multipart Types

MIME provides for a number of "multipart" types -- encapsulations of several entities within a single message's Entity-Body. The multipart types registered by IANA [15] do not have any special meaning for HTTP/1.0, though user agents may need to understand each type in order to correctly interpret the purpose of each body-part. An HTTP user agent should follow the same or similar behavior as a MIME user agent does upon receipt of a multipart type. HTTP servers should not assume that all HTTP clients are prepared to handle multipart types.

All multipart types share a common syntax and must include a boundary parameter as part of the media type value. The message body is itself a protocol element and must therefore use only CRLF to represent line breaks between body-parts. Multipart body-parts may contain HTTP header fields which are significant to the meaning of that part.

Next: 3.7 Product Tokens

Connected: An Internet Encyclopedia
RFC 1945 - 3.6.2 Multipart Types