GNURLOPT_T...R_ENCODING(3)

✨ GNURLOPT_T...R_ENCODING(3) ✨

okay so bestie, real talk — this whole page lives in the curl_easy_setopt options manual, and the star of the show is CURLOPT_TRANSFER_ENCODING. yes the header is squished like GNURLOPT_T...R_ENCODING(3), no that's not a typo, that's just how the terminal eats it 💅

---

🎀 NAME 🎀

CURLOPT_TRANSFER_ENCODING — the one where you ask for HTTP Transfer Encoding 🦋

---

🌸 SYNOPSIS 🌸

#include <gnurl/curl.h>

CURLcode curl_easy_setopt(CURL *handle, CURLOPT_TRANSFER_ENCODING, long
enable);

---

💖 DESCRIPTION 💖

okay so you pass a long — set it to 1L to turn it on, or 0 to turn it off. that's it, that's the vibe 🫶

what it actually does: it adds a request for compressed Transfer Encoding into your outgoing HTTP request. and like — if the server supports it and is feeling generous, it can clap back with an HTTP response sent using a compressed Transfer-Encoding. and the best part? libcurl automatically uncompresses that for you on reception. no cap, you don't have to do anything ✨

now here's the tea on why Transfer-Encoding is a whole different creature from the Content-Encoding you'd ask for with CURLOPT_ACCEPT_ENCODING(3): a Transfer-Encoding is strictly meant to be for the transfer itself, so it MUST be decoded before the data arrives in the client. non-negotiable, it's giving main character rules 👑

and historically? Transfer-Encoding has been much less used and supported — by both HTTP clients AND HTTP servers. so like, lowkey rare. highkey iconic when it works. 💀

---

🍓 DEFAULT 🍓

0

(off by default, she's sleeping 😴)

---

🌈 PROTOCOLS 🌈

HTTP

---

🔥 EXAMPLE 🔥

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);
}

look at her go 😭✨

---

⭐ AVAILABILITY ⭐

Added in 7.21.6 — vintage but still slaying 🎀

---

💜 RETURN VALUE 💜

Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not. simple as that, bestie 🙈

---

👑 SEE ALSO 👑

• CURLOPT_ACCEPT_ENCODING(3)
• CURLOPT_HTTP_TRANSFER_DECODING(3)

---

💀 heads up: because Transfer-Encoding MUST be decoded before the data arrives in the client, this is not the same game as Content-Encoding. don't mix them up, i'm begging 🫶

---

mwah 💋 that's the whole page — brought to you by libcurl 7.37.0, dated 19 Jun 2014, and the letters GNURLOPT_T...R_ENCODING(3) which we simply must respect 🧚‍♀️💜