A combination of {@link #type()} and {@link #boundary()}.
The number of parts in this multipart body.
Appends a quoted-string to a StringBuilder.
The "multipart/alternative" type is syntactically identical to "multipart/mixed", but the semantics are different. In particular, each of the body parts is an "alternative" version of the same information.
This type is syntactically identical to "multipart/mixed", but the semantics are different. In particular, in a digest, the default {@code Content-Type} value for a body part is changed from "text/plain" to "message/rfc822".
The media-type multipart/form-data follows the rules of all multipart MIME data streams as outlined in RFC 2046. In forms, there are a series of fields to be supplied by the user who fills out the form. Each field has a name. Within a given form, the names are unique.
The "mixed" subtype of "multipart" is intended for use when the body parts are independent and need to be bundled in a particular order. Any "multipart" subtypes that an implementation does not recognize must be treated as being of subtype "mixed".
This type is syntactically identical to "multipart/mixed", but the semantics are different. In particular, in a parallel entity, the order of body parts is not significant.
Returns the number of bytes that will be written to {@code sink} in a call to {@link #writeTo}, or -1 if that count is unknown.
Writes the content of this request to {@code sink}.
Returns a new request body that transmits {@code content}. If {@code contentType} is non-null and lacks a charset, this will use UTF-8.
Returns a new request body that transmits {@code content}.
Returns a new request body that transmits the content of {@code file}.
An <a href="http://www.ietf.org/rfc/rfc2387.txt">RFC 2387</a>-compliant request body.