curl_mime_encoder - set a mime part's encoder and content transfer encoding
CURLcode curl_mime_encoder(curl_mimepart * part, const
char * encoding);
curl_mime_encoder() requests a mime part's content to be encoded before being
is the part's handle to assign an encoder. encoding
pointer to a zero-terminated encoding scheme. It may be set to NULL to disable
an encoder previously attached to the part. The encoding scheme storage may
safely be reused after this function returns.
Setting a part's encoder twice is valid: only the value set by the last call is
Upon multipart rendering, the part's content is encoded according to the
pertaining scheme and a corresponding Content-Transfer-Encoding"
header is added to the part.
Supported encoding schemes are:
": the data is left unchanged, the header is added.
": header added, no data change.
": the data is unchanged, but is each byte is checked to
be a 7-bit value; if not, a read error occurs.
": Data is converted to base64 encoding, then split in
CRLF-terminated lines of at most 76 characters.
": data is encoded in quoted printable lines
of at most 76 characters. Since the resulting size of the final data cannot be
determined prior to reading the original data, it is left as unknown, causing
chunked transfer in HTTP. For the same reason, this encoder may not be used
with IMAP. This encoder targets text data that is mostly ASCII and should not
be used with other types of data.
If the original data is already encoded in such a scheme, a custom
header should be added with curl_mime_headers
() instead of setting a part encoder.
Encoding should not be applied to multiparts, thus the use of this function on a
part with content set with curl_mime_subparts
() is strongly
As long as at least one of HTTP, SMTP or IMAP is enabled. Added in 7.56.0.
CURLE_OK or a CURL error code upon failure.
/* create a mime handle */
mime = curl_mime_init(easy);
/* add a part */
part = curl_mime_addpart(mime);
/* send a file */
/* encode file data in base64 for transfer */