curl - Man Page

transfer a URL

Examples (TL;DR)

Make an HTTP GET request and dump the contents in stdout: curl https://example.com
Make an HTTP GET request, fo[L]low any 3xx redirects, and [D]ump the reply headers and contents to stdout: curl --location --dump-header - https://example.com
Download a file, saving the [O]utput under the filename indicated by the URL: curl --remote-name https://example.com/filename.zip
Send form-encoded [d]ata (POST request of type application/x-www-form-urlencoded). Use --data @file_name or --data @'-' to read from stdin: curl -X POST --data 'name=bob' http://example.com/form
Send a request with an extra header, using a custom HTTP method and over a pro[x]y (such as BurpSuite), ignoring insecure self-signed certificates: curl -k --proxy http://127.0.0.1:8080 --header 'Authorization: Bearer token' --request GET|PUT|POST|DELETE|PATCH|... https://example.com
Send data in JSON format, specifying the appropriate Content-Type [H]eader: curl --data '{"name":"bob"}' --header 'Content-Type: application/json' http://example.com/users/1234
Pass client certificate and key for a resource, skipping certificate validation: curl --cert client.pem --key key.pem --insecure https://example.com
Resolve a hostname to a custom IP address, with [v]erbose output (similar to editing the /etc/hosts file for custom DNS resolution): curl --verbose --resolve example.com:80:127.0.0.1 http://example.com

curl is a tool for transferring data from or to a server using URLs. It supports these protocols: DICT, FILE, FTP, FTPS, GOPHER, GOPHERS, HTTP, HTTPS, IMAP, IMAPS, LDAP, LDAPS, MQTT, POP3, POP3S, RTMP, RTMPS, RTSP, SCP, SFTP, SMB, SMBS, SMTP, SMTPS, TELNET, TFTP, WS and WSS.

curl is powered by libcurl for all transfer-related features. See libcurl(3) for details.

URL

The URL syntax is protocol-dependent. You find a detailed description in RFC 3986.

If you provide a URL without a leading protocol:// scheme, curl guesses what protocol you want. It then defaults to HTTP but assumes others based on often-used hostname prefixes. For example, for hostnames starting with "ftp." curl assumes you want FTP.

You can specify any amount of URLs on the command line. They are fetched in a sequential manner in the specified order unless you use -Z, --parallel. You can specify command line options and URLs mixed and in any order on the command line.

curl attempts to reuse connections when doing multiple transfers, so that getting many files from the same server do not use multiple connects and setup handshakes. This improves speed. Connection reuse can only be done for URLs specified for a single command line invocation and cannot be performed between separate curl runs.

Provide an IPv6 zone id in the URL with an escaped percentage sign. Like in

"http://[fe80::3%25eth0]/"

Everything provided on the command line that is not a command line option or its argument, curl assumes is a URL and treats it as such.

Globbing

You can specify multiple URLs or parts of URLs by writing lists within braces or ranges within brackets. We call this "globbing".

Provide a list with three different names like this:

"http://site.{one,two,three}.com"

Do sequences of alphanumeric series by using [] as in:

"ftp://ftp.example.com/file[1-100].txt"

With leading zeroes:

"ftp://ftp.example.com/file[001-100].txt"

With letters through the alphabet:

"ftp://ftp.example.com/file[a-z].txt"

Nested sequences are not supported, but you can use several ones next to each other:

"http://example.com/archive[1996-1999]/vol[1-4]/part{a,b,c}.html"

You can specify a step counter for the ranges to get every Nth number or letter:

"http://example.com/file[1-100:10].txt"

"http://example.com/file[a-z:2].txt"

When using [] or {} sequences when invoked from a command line prompt, you probably have to put the full URL within double quotes to avoid the shell from interfering with it. This also goes for other characters treated special, like for example '&', '?' and '*'.

Switch off globbing with -g, --globoff.

Variables

curl supports command line variables (added in 8.3.0). Set variables with --variable name=content or --variable name@file (where "file" can be stdin if set to a single dash (-)).

Variable contents can be expanded in option parameters using "{{name}}" if the option name is prefixed with "--expand-". This gets the contents of the variable "name" inserted, or a blank if the name does not exist as a variable. Insert "{{" verbatim in the string by prefixing it with a backslash, like "\{{".

You access and expand environment variables by first importing them. You select to either require the environment variable to be set or you can provide a default value in case it is not already set. Plain "--variable %name" imports the variable called "name" but exits with an error if that environment variable is not already set. To provide a default value if it is not set, use "--variable %name=content" or "--variable %name@content".

Example. Get the USER environment variable into the URL, fail if USER is not set:

--variable '%USER'
--expand-url = "https://example.com/api/{{USER}}/method"

When expanding variables, curl supports a set of functions that can make the variable contents more convenient to use. It can trim leading and trailing white space with "trim", it can output the contents as a JSON quoted string with "json", URL encode the string with "url" or base64 encode it with "b64". To apply functions to a variable expansion, add them colon separated to the right side of the variable. Variable content holding null bytes that are not encoded when expanded cause error.

Example: get the contents of a file called $HOME/.secret into a variable called "fix". Make sure that the content is trimmed and percent-encoded when sent as POST data:

--variable %HOME
--expand-variable fix@{{HOME}}/.secret
--expand-data "{{fix:trim:url}}"
https://example.com/

Command line variables and expansions were added in 8.3.0.

Output

If not told otherwise, curl writes the received data to stdout. It can be instructed to instead save that data into a local file, using the -o, --output or -O, --remote-name options. If curl is given multiple URLs to transfer on the command line, it similarly needs multiple options for where to save them.

curl does not parse or otherwise "understand" the content it gets or writes as output. It does no encoding or decoding, unless explicitly asked to with dedicated command line options.

Protocols

curl supports numerous protocols, or put in URL terms: schemes. Your particular build may not support them all.

DICT: Lets you lookup words using online dictionaries.
FILE: Read or write local files. curl does not support accessing file:// URL remotely, but when running on Microsoft Windows using the native UNC approach works.
FTP(S): curl supports the File Transfer Protocol with a lot of tweaks and levers. With or without using TLS.
GOPHER(S): Retrieve files.
HTTP(S): curl supports HTTP with numerous options and variations. It can speak HTTP version 0.9, 1.0, 1.1, 2 and 3 depending on build options and the correct command line options.
IMAP(S): Using the mail reading protocol, curl can download emails for you. With or without using TLS.
LDAP(S): curl can do directory lookups for you, with or without TLS.
MQTT: curl supports MQTT version 3. Downloading over MQTT equals subscribe to a topic while uploading/posting equals publish on a topic. MQTT over TLS is not supported (yet).
POP3(S): Downloading from a pop3 server means getting a mail. With or without using TLS.
RTMP(S): The Realtime Messaging Protocol is primarily used to serve streaming media and curl can download it.
RTSP: curl supports RTSP 1.0 downloads.
SCP: curl supports SSH version 2 scp transfers.
SFTP: curl supports SFTP (draft 5) done over SSH version 2.
SMB(S): curl supports SMB version 1 for upload and download.
SMTP(S): Uploading contents to an SMTP server means sending an email. With or without TLS.
TELNET: Fetching a telnet URL starts an interactive session where it sends what it reads on stdin and outputs what the server sends it.
TFTP: curl can do TFTP downloads and uploads.
WS(S): WebSocket done over HTTP/1. WSS implies that it works over HTTPS.

Progress Meter

curl normally displays a progress meter during operations, indicating the amount of transferred data, transfer speeds and estimated time left, etc. The progress meter displays the transfer rate in bytes per second. The suffixes (k, M, G, T, P) are 1024 based. For example 1k is 1024 bytes. 1M is 1048576 bytes.

curl displays this data to the terminal by default, so if you invoke curl to do an operation and it is about to write data to the terminal, it disables the progress meter as otherwise it would mess up the output mixing progress meter and response data.

If you want a progress meter for HTTP POST or PUT requests, you need to redirect the response output to a file, using shell redirect (>), -o, --output or similar.

This does not apply to FTP upload as that operation does not spit out any response data to the terminal.

If you prefer a progress bar instead of the regular meter, -#, --progress-bar is your friend. You can also disable the progress meter completely with the -s, --silent option.

Version

This man page describes curl 8.10.1. If you use a later version, chances are this man page does not fully document it. If you use an earlier version, this document tries to include version information about which specific version that introduced changes.

You can always learn which the latest curl version is by running

curl https://curl.se/info

The online version of this man page is always showing the latest incarnation: https://curl.se/docs/manpage.html

Options

Options start with one or two dashes. Many of the options require an additional value next to them. If provided text does not start with a dash, it is presumed to be and treated as a URL.

The short "single-dash" form of the options, -d for example, may be used with or without a space between it and its value, although a space is a recommended separator. The long double-dash form, -d, --data for example, requires a space between it and its value.

Short version options that do not need any additional values can be used immediately next to each other, like for example you can specify all the options -O, -L and -v at once as -OLv.

In general, all boolean options are enabled with --option and yet again disabled with --no-option. That is, you use the same option name but prefix it with "no-". However, in this list we mostly only list and show the --option version of them.

When -:, --next is used, it resets the parser state and you start again with a clean option state, except for the options that are global. Global options retain their values and meaning even after -:, --next.

The following options are global: --fail-early, --libcurl, --parallel-immediate, --parallel-max, -Z, --parallel, -#, --progress-bar, --rate, -S, --show-error, --stderr, --styled-output, --trace-ascii, --trace-config, --trace-ids, --trace-time, --trace and -v, --verbose.

All Options

--abstract-unix-socket <path>

(HTTP) Connect through an abstract Unix domain socket, instead of using the network. Note: netstat shows the path of an abstract socket prefixed with "@", however the <path> argument should not have this leading character.

If --abstract-unix-socket is provided several times, the last set value is used.

Example:

curl --abstract-unix-socket socketpath https://example.com

See also -x, --proxy.

--ntlm

(HTTP) Use NTLM authentication. The NTLM authentication method was designed by Microsoft and is used by IIS web servers. It is a proprietary protocol, reverse-engineered by clever people and implemented in curl based on their efforts. This kind of behavior should not be endorsed, you should encourage everyone who uses NTLM to switch to a public and documented authentication method instead, such as Digest.

If you want to enable NTLM for your proxy authentication, then use --proxy-ntlm.

Providing --ntlm multiple times has no extra effect.

Example:

curl --ntlm -u user:password https://example.com

--ntlm requires that libcurl is built to support TLS. This option is mutually exclusive with --basic, --negotiate, --digest and --anyauth. See also --proxy-ntlm.

--ntlm-wb

(HTTP) Deprecated option (added in 8.8.0).

Enabled NTLM much in the style --ntlm does, but handed over the authentication to a separate executable that was executed when needed.

Providing --ntlm-wb multiple times has no extra effect.

Example:

curl --ntlm-wb -u user:password https://example.com

See also -x, --proxy.

--proxy-http2

(HTTP) Negotiate HTTP/2 with an HTTPS proxy. The proxy might still only offer HTTP/1 and then curl sticks to using that version.

This has no effect for any other kinds of proxies.

Providing --proxy-http2 multiple times has no extra effect. Disable it again with --no-proxy-http2.

Example:

curl --proxy-http2 -x proxy https://example.com

--proxy-http2 requires that libcurl is built to support HTTP/2. Added in 8.1.0. See also -x, --proxy.

--proxy-insecure

Same as -k, --insecure but used in HTTPS proxy context.

Every secure connection curl makes is verified to be secure before the transfer takes place. This option makes curl skip the verification step with a proxy and proceed without checking.

When this option is not used for a proxy using HTTPS, curl verifies the proxy's TLS certificate before it continues: that the certificate contains the right name which matches the hostname and that the certificate has been signed by a CA certificate present in the cert store. See this online resource for further details: https://curl.se/docs/sslcerts.html

WARNING: using this option makes the transfer to the proxy insecure.

Providing --proxy-insecure multiple times has no extra effect. Disable it again with --no-proxy-insecure.

Example:

curl --proxy-insecure -x https://proxy https://example.com

See also -x, --proxy and -k, --insecure.

--proxy-key <key>

Specify the filename for your private key when using client certificates with your HTTPS proxy. This option is the equivalent to --key but used in HTTPS proxy context.

If --proxy-key is provided several times, the last set value is used.

Example:

curl --proxy-key here -x https://proxy https://example.com

See also --proxy-key-type and -x, --proxy.

--proxy-key-type <type>

Specify the private key file type your --proxy-key provided private key uses. DER, PEM, and ENG are supported. If not specified, PEM is assumed.

Equivalent to --key-type but used in HTTPS proxy context.

If --proxy-key-type is provided several times, the last set value is used.

Example:

curl --proxy-key-type DER --proxy-key here -x https://proxy https://example.com

See also --proxy-key and -x, --proxy.

--proxy-negotiate

Use HTTP Negotiate (SPNEGO) authentication when communicating with the given proxy. Use --negotiate for enabling HTTP Negotiate (SPNEGO) with a remote host.

Providing --proxy-negotiate multiple times has no extra effect.

Example:

curl --proxy-negotiate --proxy-user user:passwd -x proxy https://example.com

See also --proxy-anyauth, --proxy-basic and --proxy-service-name.

--proxy-ntlm

Use HTTP NTLM authentication when communicating with the given proxy. Use --ntlm for enabling NTLM with a remote host.

Providing --proxy-ntlm multiple times has no extra effect.

Example:

curl --proxy-ntlm --proxy-user user:passwd -x http://proxy https://example.com

See also --proxy-negotiate, --proxy-anyauth and -U, --proxy-user.

--proxy-pass <phrase>

Passphrase for the private key for HTTPS proxy client certificate.

Equivalent to --pass but used in HTTPS proxy context.

If --proxy-pass is provided several times, the last set value is used.

Example:

curl --proxy-pass secret --proxy-key here -x https://proxy https://example.com

See also -x, --proxy and --proxy-key.

--proxy-pinnedpubkey <hashes>

(TLS) Use the specified public key file (or hashes) to verify the proxy. This can be a path to a file which contains a single public key in PEM or DER format, or any number of base64 encoded sha256 hashes preceded by 'sha256//' and separated by ';'.

Before curl 8.10.0 this option did not work due to a bug.

If --proxy-pinnedpubkey is provided several times, the last set value is used.

Examples:

curl --proxy-pinnedpubkey keyfile https://example.com
curl --proxy-pinnedpubkey 'sha256//ce118b51897f4452dc' https://example.com

See also --pinnedpubkey and -x, --proxy.

--proxy-service-name <name>

Set the service name for SPNEGO when doing proxy authentication.

If --proxy-service-name is provided several times, the last set value is used.

Example:

curl --proxy-service-name "shrubbery" -x proxy https://example.com

See also --service-name, -x, --proxy and --proxy-negotiate.

--proxy-ssl-allow-beast

Do not work around a security flaw in the TLS1.0 protocol known as BEAST when communicating to an HTTPS proxy. If this option is not used, the TLS layer may use workarounds known to cause interoperability problems with some older server implementations.

This option only changes how curl does TLS 1.0 with an HTTPS proxy and has no effect on later TLS versions.

WARNING: this option loosens the TLS security, and by using this flag you ask for exactly that.

Equivalent to --ssl-allow-beast but used in HTTPS proxy context.

Providing --proxy-ssl-allow-beast multiple times has no extra effect. Disable it again with --no-proxy-ssl-allow-beast.

Example:

curl --proxy-ssl-allow-beast -x https://proxy https://example.com

See also --ssl-allow-beast and -x, --proxy.

--proxy-ssl-auto-client-cert

Same as --ssl-auto-client-cert but used in HTTPS proxy context.

This is only supported by Schannel.

Providing --proxy-ssl-auto-client-cert multiple times has no extra effect. Disable it again with --no-proxy-ssl-auto-client-cert.

Example:

curl --proxy-ssl-auto-client-cert -x https://proxy https://example.com

Added in 7.77.0. See also --ssl-auto-client-cert and -x, --proxy.

--proxy-tls13-ciphers <list>

(TLS) Same as --tls13-ciphers but used in HTTPS proxy context.

Specify which cipher suites to use in the connection to your HTTPS proxy when it negotiates TLS 1.3. The list of ciphers suites must specify valid ciphers. Read up on TLS 1.3 cipher suite details on this URL:

https://curl.se/docs/ssl-ciphers.html

This option is used when curl is built to use OpenSSL 1.1.1 or later, Schannel, wolfSSL, or mbedTLS 3.6.0 or later.

Before curl 8.10.0 with mbedTLS or wolfSSL, TLS 1.3 cipher suites where set by using the --proxy-ciphers option.

If --proxy-tls13-ciphers is provided several times, the last set value is used.

Example:

curl --proxy-tls13-ciphers TLS_AES_128_GCM_SHA256 -x proxy https://example.com

Added in 7.61.0. See also --proxy-ciphers, --tls13-ciphers and -x, --proxy.

--proxy-tlsauthtype <type>

Set TLS authentication type with HTTPS proxy. The only supported option is "SRP", for TLS-SRP (RFC 5054). This option works only if the underlying libcurl is built with TLS-SRP support.

Equivalent to --tlsauthtype but used in HTTPS proxy context.

If --proxy-tlsauthtype is provided several times, the last set value is used.

Example:

curl --proxy-tlsauthtype SRP -x https://proxy https://example.com

See also -x, --proxy, --proxy-tlsuser and --proxy-tlspassword.

--proxy-tlspassword <string>

Set password to use with the TLS authentication method specified with --proxy-tlsauthtype when using HTTPS proxy. Requires that --proxy-tlsuser is set.

This option does not work with TLS 1.3.

Equivalent to --tlspassword but used in HTTPS proxy context.

If --proxy-tlspassword is provided several times, the last set value is used.

Example:

curl --proxy-tlspassword passwd -x https://proxy https://example.com

See also -x, --proxy and --proxy-tlsuser.

--proxy-tlsuser <name>

Set username for use for HTTPS proxy with the TLS authentication method specified with --proxy-tlsauthtype. Requires that --proxy-tlspassword also is set.

This option does not work with TLS 1.3.

If --proxy-tlsuser is provided several times, the last set value is used.

Example:

curl --proxy-tlsuser smith -x https://proxy https://example.com

See also -x, --proxy and --proxy-tlspassword.

--proxy-tlsv1

Use at least TLS version 1.x when negotiating with an HTTPS proxy. That means TLS version 1.0 or higher

Equivalent to -1, --tlsv1 but for an HTTPS proxy context.

Providing --proxy-tlsv1 multiple times has no extra effect.

Example:

curl --proxy-tlsv1 -x https://proxy https://example.com

See also -x, --proxy.

-U, --proxy-user <user:password>

Specify the username and password to use for proxy authentication.

If you use a Windows SSPI-enabled curl binary and do either Negotiate or NTLM authentication then you can tell curl to select the username and password from your environment by specifying a single colon with this option: "-U :".

On systems where it works, curl hides the given option argument from process listings. This is not enough to protect credentials from possibly getting seen by other users on the same system as they still are visible for a moment before cleared. Such sensitive data should be retrieved from a file instead or similar and never used in clear text in a command line.

If --proxy-user is provided several times, the last set value is used.

Example:

curl --proxy-user smith:secret -x proxy https://example.com

See also -x, --proxy.

--pubkey <key>

(SFTP SCP) Public key filename. Allows you to provide your public key in this separate file.

curl attempts to automatically extract the public key from the private key file, so passing this option is generally not required. Note that this public key extraction requires libcurl to be linked against a copy of libssh2 1.2.8 or higher that is itself linked against OpenSSL.

If --pubkey is provided several times, the last set value is used.

Example:

curl --pubkey file.pub sftp://example.com/

See also --socks5.

--socks5-gssapi

Use GSS-API authentication when connecting to a SOCKS5 proxy. The GSS-API authentication is enabled by default (if curl is compiled with GSS-API support). Use --socks5-basic to force username/password authentication to SOCKS5 proxies.

Providing --socks5-gssapi multiple times has no extra effect. Disable it again with --no-socks5-gssapi.

Example:

curl --socks5-gssapi --socks5 hostname:4096 https://example.com

See also --socks5.

--socks5-gssapi-nec

As part of the GSS-API negotiation a protection mode is negotiated. RFC 1961 says in section 4.3/4.4 it should be protected, but the NEC reference implementation does not. The option --socks5-gssapi-nec allows the unprotected exchange of the protection mode negotiation.

Providing --socks5-gssapi-nec multiple times has no extra effect. Disable it again with --no-socks5-gssapi-nec.

Example:

curl --socks5-gssapi-nec --socks5 hostname:4096 https://example.com

See also --socks5.

--socks5-gssapi-service <name>

Set the service name for a socks server. Default is rcmd/server-fqdn.

If --socks5-gssapi-service is provided several times, the last set value is used.

Example:

curl --socks5-gssapi-service sockd --socks5 hostname:4096 https://example.com

See also --socks5.

--socks5-hostname <host[:port]>

Use the specified SOCKS5 proxy (and let the proxy resolve the hostname). If the port number is not specified, it is assumed at port 1080.

To specify proxy on a Unix domain socket, use localhost for host, e.g. "socks5h://localhost/path/to/socket.sock"

This option overrides any previous use of -x, --proxy, as they are mutually exclusive.

This option is superfluous since you can specify a socks5 hostname proxy with -x, --proxy using a socks5h:// protocol prefix.

If --socks5-hostname is provided several times, the last set value is used.

Example:

curl --socks5-hostname proxy.example:7000 https://example.com

Files

~/.curlrc

Default config file, see -K, --config for details.

Environment

The environment variables can be specified in lower case or upper case. The lower case version has precedence. "http_proxy" is an exception as it is only available in lower case.

Using an environment variable to set the proxy has the same effect as using the -x, --proxy option.

http_proxy [protocol://]<host>[:port]

Sets the proxy server to use for HTTP.

HTTPS_PROXY [protocol://]<host>[:port]

Sets the proxy server to use for HTTPS.

[url-protocol]_PROXY [protocol://]<host>[:port]

Sets the proxy server to use for [url-protocol], where the protocol is a protocol that curl supports and as specified in a URL. FTP, FTPS, POP3, IMAP, SMTP, LDAP, etc.

ALL_PROXY [protocol://]<host>[:port]

Sets the proxy server to use if no protocol-specific proxy is set.

NO_PROXY <comma-separated list of hosts/domains>

list of hostnames that should not go through any proxy. If set to an asterisk '*' only, it matches all hosts. Each name in this list is matched as either a domain name which contains the hostname, or the hostname itself.

This environment variable disables use of the proxy even when specified with the -x, --proxy option. That is

NO_PROXY=direct.example.com curl -x http://proxy.example.com
http://direct.example.com

accesses the target URL directly, and

NO_PROXY=direct.example.com curl -x http://proxy.example.com
http://somewhere.example.com

accesses the target URL through the proxy.

The list of hostnames can also be include numerical IP addresses, and IPv6 versions should then be given without enclosing brackets.

IP addresses can be specified using CIDR notation: an appended slash and number specifies the number of "network bits" out of the address to use in the comparison (added in 7.86.0). For example "192.168.0.0/16" would match all addresses starting with "192.168".

APPDATA <dir>

On Windows, this variable is used when trying to find the home directory. If the primary home variable are all unset.

COLUMNS <terminal width>

If set, the specified number of characters is used as the terminal width when the alternative progress-bar is shown. If not set, curl tries to figure it out using other ways.

CURL_CA_BUNDLE <file>

If set, it is used as the --cacert value. This environment variable is ignored if Schannel is used as the TLS backend.

CURL_HOME <dir>

If set, is the first variable curl checks when trying to find its home directory. If not set, it continues to check XDG_CONFIG_HOME

CURL_SSL_BACKEND <TLS backend>

If curl was built with support for "MultiSSL", meaning that it has built-in support for more than one TLS backend, this environment variable can be set to the case insensitive name of the particular backend to use when curl is invoked. Setting a name that is not a built-in alternative makes curl stay with the default.

SSL backend names (case-insensitive): bearssl, gnutls, mbedtls, openssl, rustls, schannel, secure-transport, wolfssl

HOME <dir>

If set, this is used to find the home directory when that is needed. Like when looking for the default .curlrc. CURL_HOME and XDG_CONFIG_HOME have preference.

QLOGDIR <directory name>

If curl was built with HTTP/3 support, setting this environment variable to a local directory makes curl produce qlogs in that directory, using file names named after the destination connection id (in hex). Do note that these files can become rather large. Works with the ngtcp2 and quiche QUIC backends.

SHELL

Used on VMS when trying to detect if using a DCL or a Unix shell.

SSL_CERT_DIR <dir>

If set, it is used as the --capath value. This environment variable is ignored if Schannel is used as the TLS backend.

SSL_CERT_FILE <path>

If set, it is used as the --cacert value. This environment variable is ignored if Schannel is used as the TLS backend.

SSLKEYLOGFILE <filename>

If you set this environment variable to a filename, curl stores TLS secrets from its connections in that file when invoked to enable you to analyze the TLS traffic in real time using network analyzing tools such as Wireshark. This works with the following TLS backends: OpenSSL, LibreSSL (TLS 1.2 max), BoringSSL, GnuTLS and wolfSSL.

USERPROFILE <dir>

On Windows, this variable is used when trying to find the home directory. If the other, primary, variable are all unset. If set, curl uses the path "$USERPROFILE\Application Data".

XDG_CONFIG_HOME <dir>

If CURL_HOME is not set, this variable is checked when looking for a default .curlrc file.

Proxy Protocol Prefixes

The proxy string may be specified with a protocol:// prefix to specify alternative proxy protocols.

If no protocol is specified in the proxy string or if the string does not match a supported one, the proxy is treated as an HTTP proxy.

The supported proxy protocol prefixes are as follows:

http://: Makes it use it as an HTTP proxy. The default if no scheme prefix is used.
https://: Makes it treated as an HTTPS proxy.
socks4://: Makes it the equivalent of --socks4
socks4a://: Makes it the equivalent of --socks4a
socks5://: Makes it the equivalent of --socks5
socks5h://: Makes it the equivalent of --socks5-hostname

Exit Codes

There are a bunch of different error codes and their corresponding error messages that may appear under error conditions. At the time of this writing, the exit codes are:

0: Success. The operation completed successfully according to the instructions.
1: Unsupported protocol. This build of curl has no support for this protocol.
2: Failed to initialize.
3: URL malformed. The syntax was not correct.
4: A feature or option that was needed to perform the desired request was not enabled or was explicitly disabled at build-time. To make curl able to do this, you probably need another build of libcurl.
5: Could not resolve proxy. The given proxy host could not be resolved.
6: Could not resolve host. The given remote host could not be resolved.
7: Failed to connect to host.
8: Weird server reply. The server sent data curl could not parse.
9: FTP access denied. The server denied login or denied access to the particular resource or directory you wanted to reach. Most often you tried to change to a directory that does not exist on the server.
10: FTP accept failed. While waiting for the server to connect back when an active FTP session is used, an error code was sent over the control connection or similar.
11: FTP weird PASS reply. Curl could not parse the reply sent to the PASS request.
12: During an active FTP session while waiting for the server to connect back to curl, the timeout expired.
13: FTP weird PASV reply, Curl could not parse the reply sent to the PASV request.
14: FTP weird 227 format. Curl could not parse the 227-line the server sent.
15: FTP cannot use host. Could not resolve the host IP we got in the 227-line.
16: HTTP/2 error. A problem was detected in the HTTP2 framing layer. This is somewhat generic and can be one out of several problems, see the error message for details.
17: FTP could not set binary. Could not change transfer method to binary.
18: Partial file. Only a part of the file was transferred.
19: FTP could not download/access the given file, the RETR (or similar) command failed.
21: FTP quote error. A quote command returned error from the server.
22: HTTP page not retrieved. The requested URL was not found or returned another error with the HTTP error code being 400 or above. This return code only appears if -f, --fail is used.
23: Write error. Curl could not write data to a local filesystem or similar.
25: Failed starting the upload. For FTP, the server typically denied the STOR command.
26: Read error. Various reading problems.
27: Out of memory. A memory allocation request failed.
28: Operation timeout. The specified time-out period was reached according to the conditions.
30: FTP PORT failed. The PORT command failed. Not all FTP servers support the PORT command, try doing a transfer using PASV instead.
31: FTP could not use REST. The REST command failed. This command is used for resumed FTP transfers.
33: HTTP range error. The range "command" did not work.
34: HTTP post error. Internal post-request generation error.
35: SSL connect error. The SSL handshaking failed.
36: Bad download resume. Could not continue an earlier aborted download.
37: FILE could not read file. Failed to open the file. Permissions?
38: LDAP cannot bind. LDAP bind operation failed.
39: LDAP search failed.
41: Function not found. A required LDAP function was not found.
42: Aborted by callback. An application told curl to abort the operation.
43: Internal error. A function was called with a bad parameter.
45: Interface error. A specified outgoing interface could not be used.
47: Too many redirects. When following redirects, curl hit the maximum amount.
48: Unknown option specified to libcurl. This indicates that you passed a weird option to curl that was passed on to libcurl and rejected. Read up in the manual!
49: Malformed telnet option.
52: The server did not reply anything, which here is considered an error.
53: SSL crypto engine not found.
54: Cannot set SSL crypto engine as default.
55: Failed sending network data.
56: Failure in receiving network data.
58: Problem with the local certificate.
59: Could not use specified SSL cipher.
60: Peer certificate cannot be authenticated with known CA certificates.
61: Unrecognized transfer encoding.
63: Maximum file size exceeded.
64: Requested FTP SSL level failed.
65: Sending the data requires a rewind that failed.
66: Failed to initialize SSL Engine.
67: The username, password, or similar was not accepted and curl failed to log in.
68: File not found on TFTP server.
69: Permission problem on TFTP server.
70: Out of disk space on TFTP server.
71: Illegal TFTP operation.
72: Unknown TFTP transfer ID.
73: File already exists (TFTP).
74: No such user (TFTP).
77: Problem reading the SSL CA cert (path? access rights?).
78: The resource referenced in the URL does not exist.
79: An unspecified error occurred during the SSH session.
80: Failed to shut down the SSL connection.
82: Could not load CRL file, missing or wrong format.
83: Issuer check failed.
84: The FTP PRET command failed.
85: Mismatch of RTSP CSeq numbers.
86: Mismatch of RTSP Session Identifiers.
87: Unable to parse FTP file list.
88: FTP chunk callback reported error.
89: No connection available, the session is queued.
90: SSL public key does not matched pinned public key.
91: Invalid SSL certificate status.
92: Stream error in HTTP/2 framing layer.
93: An API function was called from inside a callback.
94: An authentication function returned an error.
95: A problem was detected in the HTTP/3 layer. This is somewhat generic and can be one out of several problems, see the error message for details.
96: QUIC connection error. This error may be caused by an SSL library error. QUIC is the protocol used for HTTP/3 transfers.
97: Proxy handshake error.
98: A client-side certificate is required to complete the TLS handshake.
99: Poll or select returned fatal error.
100: A value or data field grew larger than allowed.
XX: More error codes might appear here in future releases. The existing ones are meant to never change.

curl - Man Page

Examples (TL;DR)

Synopsis

Description

URL

Globbing

Variables

Output

Protocols

Progress Meter

Version

Options

All Options

Files

Environment

Proxy Protocol Prefixes

Exit Codes

Bugs

Authors

WWW

See Also

Referenced By