CURLOPT_PROXY(3)
π CURLOPT_PROXY
okay so bestie, this is the <curl/curl.h> page about telling curl which proxy to use β the manual is CURLOPT_PROXY and it lives in the Library Functions Manual and honestly it's a whole vibe β¨
β¨ SYNOPSIS β¨
#include <curl/curl.h>
CURLcode curl_easy_setopt(CURL *handle, CURLOPT_PROXY, char *proxy);
πΈ DESCRIPTION πΈ
So you wanna set the proxy for transfers on this easy handle? Slay, here's the tea π. The parameter should be a char * pointing at a null-terminated string holding the hostname or a dotted numerical IP address. If you're giving it a numerical IPv6 address you must write it inside [brackets] β no cap.
Wanna include the port in that string? Just append :[port] to the end of the host name. The proxy's port number may optionally (but honestly, discouraged) be specified with the separate option CURLOPT_PROXYPORT(3). And if you don't specify it at all? libcurl defaults to using port 1080 for proxies. iconic of it π
You can also prefix the proxy string with [scheme]:// to specify which kind of proxy you're using π¦
Set this option multiple times and the last set string overrides the previous ones β later is louder, periodt. Set it to NULL to disable its use again.
Good news: the application does not have to keep the string around after setting this option. libcurl copies it, she's got it from here π«Ά
Now the schemes, bestie β each one is its own little moment:
http://β HTTP Proxy. This is the default when no scheme or proxy type is specified.https://β HTTPS Proxy. (Added in7.52.0for OpenSSL and GnuTLS. Since7.87.0, it also works for mbedTLS, Rustls, Schannel and wolfSSL.) This uses HTTP/1 by default. SettingCURLOPT_PROXYTYPE(3)toCURLPROXY_HTTPS2allows libcurl to negotiate using HTTP/2 with proxy.socks4://β SOCKS4 Proxy.socks4a://β SOCKS4a Proxy. Proxy resolves URL hostname.socks5://β SOCKS5 Proxy.socks5h://β SOCKS5 Proxy. Proxy resolves URL hostname.
If you don't give a scheme prefix, CURLOPT_PROXYTYPE(3) can be used to specify which kind of proxy the string identifies. iykyk π
When you tell the library to use an HTTP proxy, libcurl transparently converts operations to HTTP even if you specify an FTP URL etc. Lowkey this can have an impact on what other features of the library you can use, such as CURLOPT_QUOTE(3) and similar FTP specifics that do not work unless you tunnel through the HTTP proxy. Such tunneling is activated with CURLOPT_HTTPPROXYTUNNEL(3) π§
Setting the proxy string to "" (an empty string) explicitly disables the use of a proxy β even if there is an environment variable set for it. Empty string said "not today" π
Unix domain sockets are supported for SOCKS proxies! Set localhost for the host part and append the absolute path to the domain socket. For example:
socks5h://localhost/path/to/socket.sock
When you set a hostname to use, do not assume that there is any particular single port number used widely for proxies. Specify it. fr fr, just specify it π
When a proxy is used, the active FTP mode as set with CUROPT_FTPPORT(3), cannot be used.
Doing FTP over an HTTP proxy without CURLOPT_HTTPPROXYTUNNEL(3) set makes libcurl do HTTP with an FTP URL over the proxy. For such transfers, common FTP specific options do not work, for example CURLOPT_USE_SSL(3). Sad but true π
π Authentication
The proxy can also be specified with its associated credentials, like for ordinary URLs, in the style:
scheme://username:password@hostname
Alternatively, set them using CURLOPT_PROXYUSERNAME(3) and CURLOPT_PROXYPASSWORD(3) π
π Environment variables
libcurl respects the proxy environment variables named http_proxy, ftp_proxy, sftp_proxy etc. If set, libcurl uses the specified proxy for that URL scheme. For an "FTP://" URL, the ftp_proxy is considered. all_proxy is used if no protocol specific proxy was set β
If no_proxy (or NO_PROXY) is set, it is the exact equivalent of setting the CURLOPT_NOPROXY(3) option.
And important, bestie: the CURLOPT_PROXY(3) and CURLOPT_NOPROXY(3) options override environment variables. Main character energy π
π DEFAULT π
NULL
π¦ PROTOCOLS π¦
This functionality affects all supported protocols. all of them. every single one π
β¨ EXAMPLE β¨
int main(void)
{
CURL *curl = curl_easy_init();
if(curl) {
curl_easy_setopt(curl, CURLOPT_URL, "https://example.com/file.txt");
curl_easy_setopt(curl, CURLOPT_PROXY, "http://proxy.example:80");
curl_easy_perform(curl);
}
}
look at her go π₯Ή
π HISTORY π
- Since
7.14.1the proxy environment variable names can include the protocol scheme. - Since
7.21.7the proxy string supports the socks protocols as "schemes". - Since
7.50.2, unsupported schemes in proxy strings cause libcurl to return error.
π« AVAILABILITY π«
Added in curl 7.1. she's been around forever, a true icon π
π₯ RETURN VALUE π₯
curl_easy_setopt(3) returns a CURLcode indicating success or error.
CURLE_OK (0) means everything was OK β yay π β and non-zero means an error occurred, so go see libcurl-errors(3).
πΈ SEE ALSO πΈ
that's the whole page, bestie!! this one's from libcurl, dated 2026-10-12, and it's literally the CURLOPT_PROXY(3) manual β go configure your proxy and slay π
β¨π«Ά
π¦ where this page comes from
- fedora 44: libcurl-devel 8.18.0-14.fc44 Β· curl
- fedora 44: libcurl-devel 8.18.0-14.fc44 Β· curl
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms