Adds a new MIME part containing body to multipart, using
"Content-Disposition: form-data", as per the HTML forms
specification. See soup_form_request_new_from_multipart() for more
details.
the name of the control associated with this file
the name of the file, or %NULL if not known
the MIME type of the file, or %NULL if not known
the file data
Adds a new MIME part containing data to multipart, using
"Content-Disposition: form-data", as per the HTML forms
specification. See soup_form_request_new_from_multipart() for more
details.
the name of the control associated with data
the body data
Adds a new MIME part to multipart with the given headers and body.
(The multipart will make its own copies of headers and body, so
you should free your copies if you are not using them for anything
else.)
the MIME part headers
the MIME part body
Frees multipart
Gets the number of body parts in multipart
Gets the indicated body part from multipart.
the part number to get (counting from 0)
Serializes multipart to dest_headers and dest_body.
the headers of the HTTP message to serialize multipart to
the body of the HTTP message to serialize multipart to
Parses headers and body to form a new #SoupMultipart
the headers of the HTTP message to parse
the body of the HTTP message to parse
Represents a multipart HTTP message body, parsed according to the syntax of RFC 2046. Of particular interest to HTTP aremultipart/byte-ranges and
multipart/form-data .
Although the headers of a #SoupMultipart body part will contain the full headers from that body part, libsoup does not interpret them according to MIME rules. For example, each body part is assumed to have "binary" Content-Transfer-Encoding, even if its headers explicitly state otherwise. In other words, don't try to use #SoupMultipart for handling real MIME multiparts.