table of contents
- buster 7.64.0-4+deb10u2
- buster-backports 7.74.0-1.2~bpo10+1
- testing 7.74.0-1.2
- unstable 7.74.0-1.3
CURLOPT_TRANSFER_ENCODING(3) | curl_easy_setopt options | CURLOPT_TRANSFER_ENCODING(3) |
NAME¶
CURLOPT_TRANSFER_ENCODING - ask for HTTP Transfer EncodingSYNOPSIS¶
#include <curl/curl.h>CURLcode curl_easy_setopt(CURL *handle, CURLOPT_TRANSFER_ENCODING, long enable);
DESCRIPTION¶
Pass a long set to 1L to enable or 0 to disable.Adds a request for compressed Transfer Encoding in the outgoing HTTP request. If the server supports this and so desires, it can respond with the HTTP response sent using a compressed Transfer-Encoding that will be automatically uncompressed by libcurl on reception.
Transfer-Encoding differs slightly from the Content-Encoding you ask for with CURLOPT_ACCEPT_ENCODING(3) in that a Transfer-Encoding is strictly meant to be for the transfer and thus MUST be decoded before the data arrives in the client. Traditionally, Transfer-Encoding has been much less used and supported by both HTTP clients and HTTP servers.
DEFAULT¶
0PROTOCOLS¶
HTTPEXAMPLE¶
CURL *curl = curl_easy_init(); if(curl) { curl_easy_setopt(curl, CURLOPT_URL, "http://example.com"); curl_easy_setopt(curl, CURLOPT_TRANSFER_ENCODING, 1L); curl_easy_perform(curl); }
AVAILABILITY¶
Added in 7.21.6RETURN VALUE¶
Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not.SEE ALSO¶
CURLOPT_ACCEPT_ENCODING(3), CURLOPT_HTTP_TRANSFER_DECODING(3),May 15, 2017 | libcurl 7.64.0 |