| 1 |
.SH FILES |
| 2 |
.I ~/.curlrc |
| 3 |
.RS |
| 4 |
Default config file, see --config for details. |
| 5 |
.SH ENVIRONMENT |
| 6 |
The environment variables can be specified in lower case or upper case. The |
| 7 |
lower case version has precedence. http_proxy is an exception as it is only |
| 8 |
available in lower case. |
| 9 |
|
| 10 |
Using an environment variable to set the proxy has the same effect as using |
| 11 |
the --proxy option. |
| 12 |
|
| 13 |
.IP "http_proxy [protocol://]<host>[:port]" |
| 14 |
Sets the proxy server to use for HTTP. |
| 15 |
.IP "HTTPS_PROXY [protocol://]<host>[:port]" |
| 16 |
Sets the proxy server to use for HTTPS. |
| 17 |
.IP "[url-protocol]_PROXY [protocol://]<host>[:port]" |
| 18 |
Sets the proxy server to use for [url-protocol], where the protocol is a |
| 19 |
protocol that curl supports and as specified in a URL. FTP, FTPS, POP3, IMAP, |
| 20 |
SMTP, LDAP etc. |
| 21 |
.IP "ALL_PROXY [protocol://]<host>[:port]" |
| 22 |
Sets the proxy server to use if no protocol-specific proxy is set. |
| 23 |
.IP "NO_PROXY <comma-separated list of hosts/domains>" |
| 24 |
list of host names that shouldn't go through any proxy. If set to an asterisk |
| 25 |
\&'*' only, it matches all hosts. Each name in this list is matched as either |
| 26 |
a domain name which contains the hostname, or the hostname itself. |
| 27 |
|
| 28 |
This environment variable disables use of the proxy even when specified with |
| 29 |
the --proxy option. That is |
| 30 |
.B NO_PROXY=direct.example.com curl -x http://proxy.example.com |
| 31 |
.B http://direct.example.com |
| 32 |
accesses the target URL directly, and |
| 33 |
.B NO_PROXY=direct.example.com curl -x http://proxy.example.com |
| 34 |
.B http://somewhere.example.com |
| 35 |
accesses the target URL through the proxy. |
| 36 |
|
| 37 |
The list of host names can also be include numerical IP addresses, and IPv6 |
| 38 |
versions should then be given without enclosing brackets. |
| 39 |
|
| 40 |
.SH "PROXY PROTOCOL PREFIXES" |
| 41 |
Since curl version 7.21.7, the proxy string may be specified with a |
| 42 |
protocol:// prefix to specify alternative proxy protocols. |
| 43 |
|
| 44 |
If no protocol is specified in the proxy string or if the string doesn't match |
| 45 |
a supported one, the proxy will be treated as an HTTP proxy. |
| 46 |
|
| 47 |
The supported proxy protocol prefixes are as follows: |
| 48 |
.IP "http://" |
| 49 |
Makes it use it as an HTTP proxy. The default if no scheme prefix is used. |
| 50 |
.IP "https://" |
| 51 |
Makes it treated as an \fBHTTPS\fP proxy. |
| 52 |
.IP "socks4://" |
| 53 |
Makes it the equivalent of --socks4 |
| 54 |
.IP "socks4a://" |
| 55 |
Makes it the equivalent of --socks4a |
| 56 |
.IP "socks5://" |
| 57 |
Makes it the equivalent of --socks5 |
| 58 |
.IP "socks5h://" |
| 59 |
Makes it the equivalent of --socks5-hostname |
| 60 |
.SH EXIT CODES |
| 61 |
There are a bunch of different error codes and their corresponding error |
| 62 |
messages that may appear during bad conditions. At the time of this writing, |
| 63 |
the exit codes are: |
| 64 |
.IP 1 |
| 65 |
Unsupported protocol. This build of curl has no support for this protocol. |
| 66 |
.IP 2 |
| 67 |
Failed to initialize. |
| 68 |
.IP 3 |
| 69 |
URL malformed. The syntax was not correct. |
| 70 |
.IP 4 |
| 71 |
A feature or option that was needed to perform the desired request was not |
| 72 |
enabled or was explicitly disabled at build-time. To make curl able to do |
| 73 |
this, you probably need another build of libcurl! |
| 74 |
.IP 5 |
| 75 |
Couldn't resolve proxy. The given proxy host could not be resolved. |
| 76 |
.IP 6 |
| 77 |
Couldn't resolve host. The given remote host was not resolved. |
| 78 |
.IP 7 |
| 79 |
Failed to connect to host. |
| 80 |
.IP 8 |
| 81 |
Weird server reply. The server sent data curl couldn't parse. |
| 82 |
.IP 9 |
| 83 |
FTP access denied. The server denied login or denied access to the particular |
| 84 |
resource or directory you wanted to reach. Most often you tried to change to a |
| 85 |
directory that doesn't exist on the server. |
| 86 |
.IP 10 |
| 87 |
FTP accept failed. While waiting for the server to connect back when an active |
| 88 |
FTP session is used, an error code was sent over the control connection or |
| 89 |
similar. |
| 90 |
.IP 11 |
| 91 |
FTP weird PASS reply. Curl couldn't parse the reply sent to the PASS request. |
| 92 |
.IP 12 |
| 93 |
During an active FTP session while waiting for the server to connect back to |
| 94 |
curl, the timeout expired. |
| 95 |
.IP 13 |
| 96 |
FTP weird PASV reply, Curl couldn't parse the reply sent to the PASV request. |
| 97 |
.IP 14 |
| 98 |
FTP weird 227 format. Curl couldn't parse the 227-line the server sent. |
| 99 |
.IP 15 |
| 100 |
FTP can't get host. Couldn't resolve the host IP we got in the 227-line. |
| 101 |
.IP 16 |
| 102 |
HTTP/2 error. A problem was detected in the HTTP2 framing layer. This is |
| 103 |
somewhat generic and can be one out of several problems, see the error message |
| 104 |
for details. |
| 105 |
.IP 17 |
| 106 |
FTP couldn't set binary. Couldn't change transfer method to binary. |
| 107 |
.IP 18 |
| 108 |
Partial file. Only a part of the file was transferred. |
| 109 |
.IP 19 |
| 110 |
FTP couldn't download/access the given file, the RETR (or similar) command |
| 111 |
failed. |
| 112 |
.IP 21 |
| 113 |
FTP quote error. A quote command returned error from the server. |
| 114 |
.IP 22 |
| 115 |
HTTP page not retrieved. The requested url was not found or returned another |
| 116 |
error with the HTTP error code being 400 or above. This return code only |
| 117 |
appears if --fail is used. |
| 118 |
.IP 23 |
| 119 |
Write error. Curl couldn't write data to a local filesystem or similar. |
| 120 |
.IP 25 |
| 121 |
FTP couldn't STOR file. The server denied the STOR operation, used for FTP |
| 122 |
uploading. |
| 123 |
.IP 26 |
| 124 |
Read error. Various reading problems. |
| 125 |
.IP 27 |
| 126 |
Out of memory. A memory allocation request failed. |
| 127 |
.IP 28 |
| 128 |
Operation timeout. The specified time-out period was reached according to the |
| 129 |
conditions. |
| 130 |
.IP 30 |
| 131 |
FTP PORT failed. The PORT command failed. Not all FTP servers support the PORT |
| 132 |
command, try doing a transfer using PASV instead! |
| 133 |
.IP 31 |
| 134 |
FTP couldn't use REST. The REST command failed. This command is used for |
| 135 |
resumed FTP transfers. |
| 136 |
.IP 33 |
| 137 |
HTTP range error. The range "command" didn't work. |
| 138 |
.IP 34 |
| 139 |
HTTP post error. Internal post-request generation error. |
| 140 |
.IP 35 |
| 141 |
SSL connect error. The SSL handshaking failed. |
| 142 |
.IP 36 |
| 143 |
Bad download resume. Couldn't continue an earlier aborted download. |
| 144 |
.IP 37 |
| 145 |
FILE couldn't read file. Failed to open the file. Permissions? |
| 146 |
.IP 38 |
| 147 |
LDAP cannot bind. LDAP bind operation failed. |
| 148 |
.IP 39 |
| 149 |
LDAP search failed. |
| 150 |
.IP 41 |
| 151 |
Function not found. A required LDAP function was not found. |
| 152 |
.IP 42 |
| 153 |
Aborted by callback. An application told curl to abort the operation. |
| 154 |
.IP 43 |
| 155 |
Internal error. A function was called with a bad parameter. |
| 156 |
.IP 45 |
| 157 |
Interface error. A specified outgoing interface could not be used. |
| 158 |
.IP 47 |
| 159 |
Too many redirects. When following redirects, curl hit the maximum amount. |
| 160 |
.IP 48 |
| 161 |
Unknown option specified to libcurl. This indicates that you passed a weird |
| 162 |
option to curl that was passed on to libcurl and rejected. Read up in the |
| 163 |
manual! |
| 164 |
.IP 49 |
| 165 |
Malformed telnet option. |
| 166 |
.IP 51 |
| 167 |
The peer's SSL certificate or SSH MD5 fingerprint was not OK. |
| 168 |
.IP 52 |
| 169 |
The server didn't reply anything, which here is considered an error. |
| 170 |
.IP 53 |
| 171 |
SSL crypto engine not found. |
| 172 |
.IP 54 |
| 173 |
Cannot set SSL crypto engine as default. |
| 174 |
.IP 55 |
| 175 |
Failed sending network data. |
| 176 |
.IP 56 |
| 177 |
Failure in receiving network data. |
| 178 |
.IP 58 |
| 179 |
Problem with the local certificate. |
| 180 |
.IP 59 |
| 181 |
Couldn't use specified SSL cipher. |
| 182 |
.IP 60 |
| 183 |
Peer certificate cannot be authenticated with known CA certificates. |
| 184 |
.IP 61 |
| 185 |
Unrecognized transfer encoding. |
| 186 |
.IP 62 |
| 187 |
Invalid LDAP URL. |
| 188 |
.IP 63 |
| 189 |
Maximum file size exceeded. |
| 190 |
.IP 64 |
| 191 |
Requested FTP SSL level failed. |
| 192 |
.IP 65 |
| 193 |
Sending the data requires a rewind that failed. |
| 194 |
.IP 66 |
| 195 |
Failed to initialise SSL Engine. |
| 196 |
.IP 67 |
| 197 |
The user name, password, or similar was not accepted and curl failed to log in. |
| 198 |
.IP 68 |
| 199 |
File not found on TFTP server. |
| 200 |
.IP 69 |
| 201 |
Permission problem on TFTP server. |
| 202 |
.IP 70 |
| 203 |
Out of disk space on TFTP server. |
| 204 |
.IP 71 |
| 205 |
Illegal TFTP operation. |
| 206 |
.IP 72 |
| 207 |
Unknown TFTP transfer ID. |
| 208 |
.IP 73 |
| 209 |
File already exists (TFTP). |
| 210 |
.IP 74 |
| 211 |
No such user (TFTP). |
| 212 |
.IP 75 |
| 213 |
Character conversion failed. |
| 214 |
.IP 76 |
| 215 |
Character conversion functions required. |
| 216 |
.IP 77 |
| 217 |
Problem with reading the SSL CA cert (path? access rights?). |
| 218 |
.IP 78 |
| 219 |
The resource referenced in the URL does not exist. |
| 220 |
.IP 79 |
| 221 |
An unspecified error occurred during the SSH session. |
| 222 |
.IP 80 |
| 223 |
Failed to shut down the SSL connection. |
| 224 |
.IP 82 |
| 225 |
Could not load CRL file, missing or wrong format (added in 7.19.0). |
| 226 |
.IP 83 |
| 227 |
Issuer check failed (added in 7.19.0). |
| 228 |
.IP 84 |
| 229 |
The FTP PRET command failed |
| 230 |
.IP 85 |
| 231 |
RTSP: mismatch of CSeq numbers |
| 232 |
.IP 86 |
| 233 |
RTSP: mismatch of Session Identifiers |
| 234 |
.IP 87 |
| 235 |
unable to parse FTP file list |
| 236 |
.IP 88 |
| 237 |
FTP chunk callback reported error |
| 238 |
.IP 89 |
| 239 |
No connection available, the session will be queued |
| 240 |
.IP 90 |
| 241 |
SSL public key does not matched pinned public key |
| 242 |
.IP 91 |
| 243 |
Invalid SSL certificate status. |
| 244 |
.IP 92 |
| 245 |
Stream error in HTTP/2 framing layer. |
| 246 |
.IP XX |
| 247 |
More error codes will appear here in future releases. The existing ones |
| 248 |
are meant to never change. |
| 249 |
.SH AUTHORS / CONTRIBUTORS |
| 250 |
Daniel Stenberg is the main author, but the whole list of contributors is |
| 251 |
found in the separate THANKS file. |
| 252 |
.SH WWW |
| 253 |
https://curl.haxx.se |
| 254 |
.SH "SEE ALSO" |
| 255 |
.BR ftp (1), |
| 256 |
.BR wget (1) |