curl.1 - OpenGrok cross reference for /external/curl/docs/curl.1

Lines Matching +full:ipv4 +full:- +full:single +full:- +full:target
8 .\" * Copyright (C) 1998 - 2018, Daniel Stenberg, <daniel@haxx.se>, et al.
28 curl \- transfer a URL
43 curl is powered by libcurl for all transfer-related features. See
46 The URL syntax is protocol-dependent. You'll find a detailed description in
56   ftp://ftp.example.com/file[1-100].txt
58   ftp://ftp.example.com/file[001-100].txt    (with leading zeros)
60   ftp://ftp.example.com/file[a-z].txt
65   http://example.com/archive[1996-1999]/vol[1-4]/part{a,b,c}.html
74   http://example.com/file[1-100:10].txt
76   http://example.com/file[a-z:2].txt
90 based on often-used host name prefixes. For example, for host names starting
97 curl will attempt to re-use connections for multiple file transfers, so that
100 specified on a single command line and cannot be used between separate curl
115 redirect the response output to a file, using shell redirect (>), \fI-o, --output\fP or
121 If you prefer a progress "bar" instead of the regular meter, \fI-#, --progress-bar\fP is
123 \fI-s, --silent\fP option.
128 The short "single-dash" form of the options, -d for example, may be used with
130 separator. The long "double-dash" form, \fI-d, --data\fP for example, requires a space
135 options -O, -L and -v at once as -OLv.
137 In general, all boolean options are enabled with --\fBoption\fP and yet again
138 disabled with --\fBno-\fPoption. That is, you use the exact same option name
139 but prefix it with "no-". However, in this list we mostly only list and show
140 the --option version of them. (This concept with --no options was added in
143 .IP "--abstract-unix-socket <path>"
149 .IP "--alt-svc <file name>"
152 This option enables the alt-svc parser in curl. If the file name points to an
153 existing alt-svc cache file, that will be used. After a completed transfer,
163 .IP "--anyauth"
166 request and checking the response-headers, thus possibly inducing an extra
167 network round-trip. This is used instead of setting a specific authentication
168 method, which you can do with \fI--basic\fP, \fI--digest\fP, \fI--ntlm\fP, and \fI--negotiate\fP.
170 Using \fI--anyauth\fP is not recommended if you do uploads from stdin, since it may
175 Used together with \fI-u, --user\fP.
177 See also \fI--proxy-anyauth\fP and \fI--basic\fP and \fI--digest\fP.
178 .IP "-a, --append"
179 (FTP SFTP) When used in an upload, this makes curl append to the target file instead of
182 .IP "--basic"
186 \fI--ntlm\fP, \fI--digest\fP, or \fI--negotiate\fP).
188 Used together with \fI-u, --user\fP.
190 See also \fI--proxy-basic\fP.
191 .IP "--cacert <file>"
202 \'curl-ca-bundle.crt\', either in the same directory as curl.exe, or in the
220 .IP "--capath <dir>"
225 c_rehash utility supplied with OpenSSL. Using \fI--capath\fP can allow
226 OpenSSL-powered curl to make SSL-connections much more efficiently than using
227 \fI--cacert\fP if the --cacert file contains many CA certificates.
231 .IP "--cert-status"
242 .IP "--cert-type <type>"
248 See also \fI-E, --cert\fP and \fI--key\fP and \fI--key-type\fP.
249 .IP "-E, --cert <certificate[:password]>"
251 with HTTPS, FTPS or another SSL-based protocol. The certificate must be in
255 private key and the client certificate concatenated! See \fI-E, --cert\fP and \fI--key\fP to
271 PKCS#11 URI. If a PKCS#11 URI is provided, then the \fI--engine\fP option will be set
272 as "pkcs11" if none was provided and the \fI--cert-type\fP option will be set as
277 system or user keychain, or the path to a PKCS#12-encoded certificate and
287 usually a SHA-1 hex string which you can see in certificate details. Following
294 See also \fI--cert-type\fP and \fI--key\fP and \fI--key-type\fP.
295 .IP "--ciphers <list of ciphers>"
299  https://curl.haxx.se/docs/ssl-ciphers.html
302 .IP "--compressed-ssh"
303 (SCP SFTP) Enables built-in SSH compression.
307 .IP "--compressed"
311 .IP "-K, --config <file>"
331 Specify the filename to \fI-K, --config\fP as '-' to make curl read the file from stdin.
334 it using the \fI--url\fP option, and not by simply writing the URL on its own
339 When curl is invoked, it (unless \fI-q, --disable\fP is used) checks for a default
345 Unix-like systems (which returns the home dir given the current user in your
350 in the same dir the curl executable is placed. On Unix-like systems, it will
354 # --- Example file ---
358 user-agent = "superagent/1.0"
364 # --- End of example file ---
368 .IP "--connect-timeout <seconds>"
371 will continue - if not it will exit.  Since version 7.32.0, this option
376 See also \fI-m, --max-time\fP.
377 .IP "--connect-to <HOST1:PORT1:HOST2:PORT2>"
394 See also \fI--resolve\fP and \fI-H, --header\fP. Added in 7.49.0.
395 .IP "-C, --continue-at <offset>"
401 Use "-C -" to tell curl to automatically find out where/how to resume the
406 See also \fI-r, --range\fP.
407 .IP "-c, --cookie-jar <filename>"
409 operation. Curl writes all cookies from its in-memory cookie storage to the
412 you set the file name to a single dash, "-", the cookies will be written to
416 record and use cookies. Another way to activate it is to use the \fI-b, --cookie\fP
420 won't fail or even report an error clearly. Using \fI-v, --verbose\fP will get a warning
426 .IP "-b, --cookie <data|filename>"
428 the data previously received from the server in a "Set-Cookie:" line.  The
434 you're using this in combination with the \fI-L, --location\fP option or do multiple URL
435 transfers on the same invoke. If the file name is exactly a minus ("-"), curl
439 (Set-Cookie style) or the Netscape/Mozilla cookie file format.
441 The file specified with \fI-b, --cookie\fP is only used as input. No cookies will be
442 written to the file. To store cookies, use the \fI-c, --cookie-jar\fP option.
445 occur.  If you use the NAME1=VALUE1; format, or in a file use the Set-Cookie
447 (even after redirects are followed) and cannot be modified by a server-set
450 what you intended.  To address these issues set a domain in Set-Cookie (doing
456 cookies back to a file, so using both \fI-b, --cookie\fP and \fI-c, --cookie-jar\fP in the same
458 .IP "--create-dirs"
459 When used in conjunction with the \fI-o, --output\fP option, curl will create the
461 mentioned with the \fI-o, --output\fP option, nothing else. If the --output file name
464 To create remote directories when using FTP or SFTP, try \fI--ftp-create-dirs\fP.
465 .IP "--crlf"
469 .IP "--crlfile <file>"
476 .IP "--data-ascii <data>"
477 (HTTP) This is just an alias for \fI-d, --data\fP.
478 .IP "--data-binary <data>"
482 is posted in a similar manner as \fI-d, --data\fP does, except that newlines and
485 Like \fI-d, --data\fP the default content-type sent to the server is
486 application/x-www-form-urlencoded. If you want the data to be treated as
487 arbitrary binary data by the server then set the content-type to octet-stream:
488 -H "Content-Type: application/octet-stream".
491 data as described in \fI-d, --data\fP.
492 .IP "--data-raw <data>"
493 (HTTP) This posts data similarly to \fI-d, --data\fP but without the special
496 See also \fI-d, --data\fP. Added in 7.43.0.
497 .IP "--data-urlencode <data>"
498 (HTTP) This posts data, similar to the other \fI-d, --data\fP options with the exception
499 that this performs URL-encoding.
501 To be CGI-compliant, the <data> part should begin with a \fIname\fP followed
506 This will make curl URL-encode the content and pass that on. Just be careful
510 This will make curl URL-encode the content and pass that on. The preceding =
513 This will make curl URL-encode the content part and pass that on. Note that
514 the name part is expected to be URL-encoded already.
517 URL-encode that data and pass it on in the POST.
520 URL-encode that data and pass it on in the POST. The name part gets an equal
521 sign appended, resulting in \fIname=urlencoded-file-content\fP. Note that the
522 name is expected to be URL-encoded already.
525 See also \fI-d, --data\fP and \fI--data-raw\fP. Added in 7.18.0.
526 .IP "-d, --data <data>"
530 content-type application/x-www-form-urlencoded.  Compare to \fI-F, --form\fP.
532 \fI--data-raw\fP is almost the same but does not have a special interpretation of
534 \fI--data-binary\fP option.  To URL-encode the value of a form field you may use
535 \fI--data-urlencode\fP.
539 &-symbol. Thus, using '-d name=daniel -d skill=lousy' would generate a post
543 read the data from, or - if you want curl to read the data from
545 'foobar' would thus be done with \fI-d, --data\fP @foobar. When --data is told to read
547 you don't want the @ character to have a special interpretation use \fI--data-raw\fP
550 …\fI--data-binary\fP and \fI--data-urlencode\fP and \fI--data-raw\fP. This option overrides \fI-F, …
551 .IP "--delegation <LEVEL>"
558 Delegates if and only if the OK-AS-DELEGATE flag is set in the Kerberos
563 .IP "--digest"
566 combination with the normal \fI-u, --user\fP option to set user name and password.
570 See also \fI-u, --user\fP and \fI--proxy-digest\fP and \fI--anyauth\fP. This option overrides \fI--…
571 .IP "--disable-eprt"
579 --eprt can be used to explicitly enable EPRT again and --no-eprt is an alias
580 for \fI--disable-eprt\fP.
586 passive mode you need to not use \fI-P, --ftp-port\fP or force it with \fI--ftp-pasv\fP.
587 .IP "--disable-epsv"
592 --epsv can be used to explicitly enable EPSV again and --no-epsv is an alias
593 for \fI--disable-epsv\fP.
599 active mode you need to use \fI-P, --ftp-port\fP.
600 .IP "-q, --disable"
602 file will not be read and used. See the \fI-K, --config\fP for details on the default
604 .IP "--disallow-username-in-url"
607 See also \fI--proto\fP. Added in 7.61.0.
608 .IP "--dns-interface <interface>"
610 counterpart to \fI--interface\fP (which does not affect DNS). The supplied string
613 See also \fI--dns-ipv4-addr\fP and \fI--dns-ipv6-addr\fP. \fI--dns-interface\fP requires that the u…
614 .IP "--dns-ipv4-addr <address>"
615 (DNS) Tell curl to bind to <ip-address> when making IPv4 DNS requests, so that
617 single IPv4 address.
619 See also \fI--dns-interface\fP and \fI--dns-ipv6-addr\fP. \fI--dns-ipv4-addr\fP requires that the u…
620 .IP "--dns-ipv6-addr <address>"
621 (DNS) Tell curl to bind to <ip-address> when making IPv6 DNS requests, so that
623 single IPv6 address.
625 See also \fI--dns-interface\fP and \fI--dns-ipv4-addr\fP. \fI--dns-ipv6-addr\fP requires that the u…
626 .IP "--dns-servers <addresses>"
629 may also optionally be given as \fI:<port-number>\fP after each IP
632 \fI--dns-servers\fP requires that the underlying libcurl was built to support c-ares. Added in 7.33…
633 .IP "--doh-url <URL>"
634 (all) Specifies which DNS-over-HTTPS (DOH) server to use to resolve hostnames,
638 .IP "-D, --dump-header <filename>"
643 curl invocation by using the \fI-b, --cookie\fP option! The \fI-c, --cookie-jar\fP option is a
651 See also \fI-o, --output\fP.
652 .IP "--egd-file <file>"
656 See also \fI--random-file\fP.
657 .IP "--engine <name>"
658 (TLS) Select the OpenSSL crypto engine to use for cipher operations. Use \fI--engine\fP
659 list to print a list of build-time supported engines. Note that not all (or
660 none) of the engines may be available at run-time.
661 .IP "--expect100-timeout <seconds>"
662 (HTTP) Maximum time in seconds that you allow curl to wait for a 100-continue
663 response when curl emits an Expects: 100-continue header in its request. By
667 See also \fI--connect-timeout\fP. Added in 7.47.0.
668 .IP "--fail-early"
681 This option is global and does not need to be specified for each use of \fI-:, --next\fP.
683 This option does not imply \fI-f, --fail\fP, which causes transfers to fail due to the
684 server's HTTP status code. You can combine the two options, however note \fI-f, --fail\fP
685 is not global and is therefore contained by \fI-:, --next\fP.
688 .IP "-f, --fail"
695 This method is not fail-safe and there are occasions where non-successful
698 .IP "--false-start"
708 .IP "--form-string <name=string>"
709 (HTTP SMTP IMAP) Similar to \fI-F, --form\fP except that the value string for the named parameter i…
711 the value have no special meaning. Use this in preference to \fI-F, --form\fP if
713 \&'@' or \&'<' features of \fI-F, --form\fP.
715 See also \fI-F, --form\fP.
716 .IP "-F, --form <name=content>"
717 (HTTP SMTP IMAP) For HTTP protocol family, this lets curl emulate a filled-in form in which a
719 Content-Type multipart/form-data according to RFC 2388.
731 Tell curl to read content from stdin instead of a file by using - as
734 possible resend.  Defining a part's data from a named non-regular file (such
741 form-field to which the file portrait.jpg will be the input:
743  curl -F profile=@portrait.jpg https://example.com/upload.cgi
747  curl -F name=John -F shoesize=11 https://example.com/
752  curl -F "story=<hugefile.txt" https://example.com/
754 You can also tell curl what Content-Type to use by using 'type=', in a manner
757  curl -F "web=@index.html;type=text/html" example.com
761  curl -F "name=daniel;type=text/foo" example.com
766  curl -F "file=@localfile;filename=nameinpost" example.com
768 If filename/path contains ',' or ';', it must be quoted by double-quotes like:
770  curl -F "file=@\\"localfile\\";filename=\\"nameinpost\\"" example.com
774  curl -F 'file=@"localfile";filename="nameinpost"' example.com
776 Note that if a filename/path is quoted by double-quotes, any double-quote
779 Quoting must also be applied to non-file data if it contains semicolons,
782  curl -F 'colors="red; green; blue";type=text/x-myapp' example.com
786   curl -F "submit=OK;headers=\\"X-submit-type: OK\\"" example.com
790   curl -F "submit=OK;headers=@headerfile" example.com
796 carriage-returns and trailing spaces are stripped.
801   X-header-1: this is a header
805   X-header-2: this is
812 - name can be omitted: the equal sign is the first character of the argument,
814 - if data starts with '(', this signals to start a new multipart: it can be
817 - a multipart can be terminated with a '=)' argument.
819 Example: the following command sends an SMTP mime e-mail consisting in an
823  curl -F '=(;type=multipart/alternative' \\
825          -F '=plain text message' \\
827          -F '= <body>HTML message</body>;type=text/html' \\
829       -F '=)' -F '=@textfile.txt' ...  smtp://example.com
833 Content-Transfer-Encoding header, \fI7bit\fP that only rejects 8-bit characters
834 with a transfer error, \fIquoted-printable\fP and \fIbase64\fP that encodes
838 Example: send multipart mail with a quoted-printable text message and a
841  curl -F '=text message;encoder=quoted-printable' \\
843       -F '=@localfile;encoder=base64' ... smtp://example.com
849 This option overrides \fI-d, --data\fP and \fI-I, --head\fP and \fI-T, --upload-file\fP.
850 .IP "--ftp-account <data>"
857 .IP "--ftp-alternative-to-user <command>"
864 .IP "--ftp-create-dirs"
869 See also \fI--create-dirs\fP.
870 .IP "--ftp-method <method>"
875 curl does a single CWD operation for each path part in the given URL. For deep
882 curl does one CWD with the full target directory and then operates on the file
888 .IP "--ftp-pasv"
890 behavior, but using this option can be used to override a previous \fI-P, --ftp-port\fP
895 correct \fI-P, --ftp-port\fP again.
898 unless \fI--disable-epsv\fP is used.
900 See also \fI--disable-epsv\fP. Added in 7.11.0.
901 .IP "-P, --ftp-port <address>"
914 .IP "-"
920 use of PORT with \fI--ftp-pasv\fP. Disable the attempt to use the EPRT command
921 instead of PORT by using \fI--disable-eprt\fP. EPRT is really PORT++.
923 Since 7.19.5, you can append \&":[start]-[end]\&" to the right of the address,
925 from a lower to a higher number. A single number works as well, but do note
928 See also \fI--ftp-pasv\fP and \fI--disable-eprt\fP.
929 .IP "--ftp-pret"
931 mainly drftpd, require this non-standard command for directory listings as
935 .IP "--ftp-skip-pasv-ip"
938 will re-use the same IP address it already uses for the control
943 See also \fI--ftp-pasv\fP. Added in 7.14.2.
944 .IP "--ftp-ssl-ccc-mode <active/passive>"
950 See also \fI--ftp-ssl-ccc\fP. Added in 7.16.2.
951 .IP "--ftp-ssl-ccc"
957 See also \fI--ssl\fP and \fI--ftp-ssl-ccc-mode\fP. Added in 7.16.1.
958 .IP "--ftp-ssl-control"
960 authentication, but non-encrypted data transfers for efficiency.  Fails the
964 .IP "-G, --get"
965 When used, this option will make all data specified with \fI-d, --data\fP, \fI--data-binary\fP
966 or \fI--data-urlencode\fP to be used in an HTTP GET request instead of the POST
970 If used in combination with \fI-I, --head\fP, the POST data will instead be appended to
976 .IP "-g, --globoff"
981 .IP "--happy-eyeballs-timeout-ms <milliseconds>"
982 Happy eyeballs is an algorithm that attempts to connect to both IPv4 and IPv6
983 addresses for dual-stack hosts, preferring IPv6 first for the number of
985 a connection attempt is made to the IPv4 address in parallel. The first
989 "It is RECOMMENDED that connection attempts be paced 150-250 ms apart to
996 .IP "--haproxy-protocol"
1005 .IP "-I, --head"
1006 (HTTP FTP FILE) Fetch the headers only! HTTP-servers feature the command HEAD which this uses
1009 .IP "-H, --header <header/@file>"
1017 the right side of the colon, as in: -H \&"Host:". If you send the custom
1018 header with no-value then its header must be terminated with a semicolon, such
1019 as \-H \&"X-Custom-Header;" to send "X-Custom-Header:".
1022 end-of-line marker, you should thus \fBnot\fP add that as a part of the header
1027 then adds a header for each line in the input file. Using @- will make curl
1030 See also the \fI-A, --user-agent\fP and \fI-e, --referer\fP options.
1032 Starting in 7.37.0, you need \fI--proxy-header\fP to send custom headers intended
1037  curl -H "X-First-Name: Joe" http://example.com/
1039 \fBWARNING\fP: headers set with this option will be set in all requests - even
1040 after redirects are followed, like when told with \fI-L, --location\fP. This can lead to
1045 .IP "-h, --help"
1048 .IP "--hostpubmd5 <md5>"
1054 .IP "--http0.9"
1058 connect with this to non-HTTP servers and still get a response since curl will
1059 simply transparently downgrade - if allowed.
1063 .IP "-0, --http1.0"
1067 This option overrides \fI--http1.1\fP and \fI--http2\fP.
1068 .IP "--http1.1"
1071 This option overrides \fI-0, --http1.0\fP and \fI--http2\fP. Added in 7.33.0.
1072 .IP "--http2-prior-knowledge"
1073 (HTTP) Tells curl to issue its non-TLS HTTP requests using HTTP/2 without HTTP/1.1
1078 …--http2-prior-knowledge\fP requires that the underlying libcurl was built to support HTTP/2. This …
1079 .IP "--http2"
1082 …--no-alpn\fP. \fI--http2\fP requires that the underlying libcurl was built to support HTTP/2. This…
1083 .IP "--ignore-content-length"
1084 (FTP HTTP) For HTTP, Ignore the Content-Length header. This is particularly useful for
1085 servers running Apache 1.x, which will report incorrect Content-Length for
1090 .IP "-i, --include"
1095 To view the request headers, consider the \fI-v, --verbose\fP option.
1097 See also \fI-v, --verbose\fP.
1098 .IP "-k, --insecure"
1110 See also \fI--proxy-insecure\fP and \fI--cacert\fP.
1111 .IP "--interface <name>"
1116  curl --interface eth0:1 https://www.example.com/
1124 See also \fI--dns-interface\fP.
1125 .IP "-4, --ipv4"
1126 This option tells curl to resolve names to IPv4 addresses only, and not for
1129 See also \fI--http1.1\fP and \fI--http2\fP. This option overrides \fI-6, --ipv6\fP.
1130 .IP "-6, --ipv6"
1132 example try IPv4.
1134 See also \fI--http1.1\fP and \fI--http2\fP. This option overrides \fI-4, --ipv4\fP.
1135 .IP "-j, --junk-session-cookies"
1141 See also \fI-b, --cookie\fP and \fI-c, --cookie-jar\fP.
1142 .IP "--keepalive-time <seconds>"
1146 TCP_KEEPINTVL socket options (meaning Linux, recent AIX, HP-UX and more). This
1147 option has no effect if \fI--no-keepalive\fP is used.
1153 .IP "--key-type <type>"
1154 (TLS) Private key file type. Specify which type your \fI--key\fP provided private key
1158 .IP "--key <key>"
1166 PKCS#11 URI. If a PKCS#11 URI is provided, then the \fI--engine\fP option will be set
1167 as "pkcs11" if none was provided and the \fI--key-type\fP option will be set as
1171 .IP "--krb <level>"
1178 \fI--krb\fP requires that the underlying libcurl was built to support Kerberos.
1179 .IP "--libcurl <file>"
1181 libcurl-using C source code written to the file that does the equivalent
1182 of what your command-line operation does!
1188 .IP "--limit-rate <speed>"
1189 Specify the maximum transfer rate you want curl to use - for both downloads
1198 If you also use the \fI-Y, --speed-limit\fP option, that option will take precedence and
1199 might cripple the rate-limiting slightly, to help keeping the speed-limit
1203 .IP "-l, --list-only"
1205 When listing an FTP directory, this switch forces a name-only view. This is
1206 especially useful if the user wants to machine-parse the contents of an FTP
1212 include sub-directories and symbolic links.
1219 Note: When combined with \fI-X, --request\fP, this option can be used to send an UIDL
1224 .IP "--local-port <num/range>"
1225 Set a preferred single number or range (FROM-TO) of local port numbers to use
1231 .IP "--location-trusted"
1232 (HTTP) Like \fI-L, --location\fP, but will allow sending the name + password to all hosts that
1237 See also \fI-u, --user\fP.
1238 .IP "-L, --location"
1242 \fI-i, --include\fP or \fI-I, --head\fP, headers from all requested pages will be shown. When
1245 intercept the user+password. See also \fI--location-trusted\fP on how to change
1247 \fI--max-redirs\fP option.
1252 re-send the following request using the same unmodified method.
1254 You can tell curl to not change the non-GET request method to GET after a 30x
1255 response by using the dedicated options for that: \fI--post301\fP, \fI--post302\fP and
1256 \fI--post303\fP.
1257 .IP "--login-options <options>"
1263 RFC 2384, RFC 5092 and IETF draft draft-earhart-url-smtp-00.txt
1268 .IP "--mail-auth <address>"
1269 (SMTP) Specify a single address. This will be used to specify the authentication
1273 See also \fI--mail-rcpt\fP and \fI--mail-from\fP. Added in 7.25.0.
1274 .IP "--mail-from <address>"
1275 (SMTP) Specify a single address that the given mail should get sent from.
1277 See also \fI--mail-rcpt\fP and \fI--mail-auth\fP. Added in 7.20.0.
1278 .IP "--mail-rcpt <address>"
1279 (SMTP) Specify a single address, user name or mailing list name. Repeat this
1290 specified using the mailing list name, such as "Friends" or "London-Office".
1294 .IP "-M, --manual"
1296 .IP "--max-filesize <bytes>"
1309 See also \fI--limit-rate\fP.
1310 .IP "--max-redirs <num>"
1311 (HTTP) Set maximum number of redirection-followings allowed. When \fI-L, --location\fP is used,
1313 limit is set to 50 redirections. Set this option to -1 to make it unlimited.
1316 .IP "-m, --max-time <seconds>"
1325 See also \fI--connect-timeout\fP.
1326 .IP "--metalink"
1336  curl --metalink http://www.example.com/example.metalink
1340  curl --metalink file://example.metalink
1343 Metalink file at the time of this writing. Also note that if \fI--metalink\fP and
1344 \fI-i, --include\fP are used together, --include will be ignored. This is because
1349 \fI--metalink\fP requires that the underlying libcurl was built to support metalink. Added in 7.27.…
1350 .IP "--negotiate"
1353 This option requires a library built with GSS-API or SSPI support. Use
1354 \fI-V, --version\fP to see if your curl supports GSS-API/SSPI or SPNEGO.
1356 When using this option, you must also provide a fake \fI-u, --user\fP option to activate
1357 the authentication code properly. Sending a '-u :' is enough as the user name
1358 and password from the \fI-u, --user\fP option aren't actually used.
1362 See also \fI--basic\fP and \fI--ntlm\fP and \fI--anyauth\fP and \fI--proxy-negotiate\fP.
1363 .IP "--netrc-file <filename>"
1364 This option is similar to \fI-n, --netrc\fP, except that you provide the path (absolute
1366 netrc file per invocation. If several \fI--netrc-file\fP options are provided,
1369 It will abide by \fI--netrc-optional\fP if specified.
1371 This option overrides \fI-n, --netrc\fP. Added in 7.21.5.
1372 .IP "--netrc-optional"
1373 Very similar to \fI-n, --netrc\fP, but this option makes the .netrc usage \fBoptional\fP
1374 and not mandatory as the \fI-n, --netrc\fP option does.
1376 See also \fI--netrc-file\fP. This option overrides \fI-n, --netrc\fP.
1377 .IP "-n, --netrc"
1383 either world- or group-readable). The environment variable "HOME" is used to
1391 .IP "-:, --next"
1397 \fI-:, --next\fP will reset all local options and only global ones will have their
1398 values survive over to the operation following the \fI-:, --next\fP instruction. Global
1399 options include \fI-v, --verbose\fP, \fI--trace\fP, \fI--trace-ascii\fP and \fI--fail-early\fP.
1401 For example, you can do both a GET and a POST in a single command line:
1403  curl www1.example.com --next -d postthis www2.example.com
1406 .IP "--no-alpn"
1411 See also \fI--no-npn\fP and \fI--http2\fP. \fI--no-alpn\fP requires that the underlying libcurl was…
1412 .IP "-N, --no-buffer"
1419 --buffer to enforce the buffering.
1420 .IP "--no-keepalive"
1425 --keepalive to enforce keepalive.
1426 .IP "--no-npn"
1431 See also \fI--no-alpn\fP and \fI--http2\fP. \fI--no-npn\fP requires that the underlying libcurl was…
1432 .IP "--no-sessionid"
1433 (TLS) Disable curl's use of SSL session-ID caching.  By default all transfers are
1435 attempting to reuse SSL session-IDs, there seem to be broken SSL
1440 --sessionid to enforce session-ID caching.
1443 .IP "--noproxy <no-proxy-list>"
1444 Comma-separated list of hosts which do not use a proxy, if one is specified.
1445 The only wildcard is a single * character, which matches all hosts, and
1456 .IP "--ntlm-wb"
1457 (HTTP) Enables NTLM much in the style \fI--ntlm\fP does, but hand over the authentication
1460 See also \fI--ntlm\fP and \fI--proxy-ntlm\fP.
1461 .IP "--ntlm"
1464 reverse-engineered by clever people and implemented in curl based on their
1470 \fI--proxy-ntlm\fP.
1474 …--proxy-ntlm\fP. \fI--ntlm\fP requires that the underlying libcurl was built to support TLS. This …
1475 .IP "--oauth2-bearer <token>"
1478 the \fI--url\fP or \fI-u, --user\fP options.
1483 .IP "-o, --output <file>"
1489  curl http://{one,two}.example.com -o "file_#1.txt"
1493  curl http://{site,host}.host[1-5].com -o "#1_#2"
1499   curl -o aa example.com -o bb example.net
1501 and the order of the -o options and the URLs doesn't matter, just that the
1502 first -o is for the first URL and so on, so the above command line can also be
1505   curl example.com example.net -o aa -o bb
1507 See also the \fI--create-dirs\fP option to create the local directories
1508 dynamically. Specifying the output as '-' (a single dash) will force the
1511 See also \fI-O, --remote-name\fP and \fI--remote-name-all\fP and \fI-J, --remote-header-name\fP.
1512 .IP "--pass <phrase>"
1516 .IP "--path-as-is"
1522 .IP "--pinnedpubkey <hashes>"
1524 peer. This can be a path to a file which contains a single public key in PEM
1545 .IP "--post301"
1547 requests when following a 301 redirection. The non-RFC behaviour is ubiquitous
1550 a redirection. This option is meaningful only when using \fI-L, --location\fP.
1552 See also \fI--post302\fP and \fI--post303\fP and \fI-L, --location\fP. Added in 7.17.1.
1553 .IP "--post302"
1555 requests when following a 302 redirection. The non-RFC behaviour is ubiquitous
1558 a redirection. This option is meaningful only when using \fI-L, --location\fP.
1560 See also \fI--post301\fP and \fI--post303\fP and \fI-L, --location\fP. Added in 7.19.1.
1561 .IP "--post303"
1565 using \fI-L, --location\fP.
1567 See also \fI--post302\fP and \fI--post301\fP and \fI-L, --location\fP. Added in 7.26.0.
1568 .IP "--preproxy [protocol://]host[:port]"
1569 Use the specified SOCKS proxy before connecting to an HTTP or HTTPS \fI-x, --proxy\fP. In
1588 .IP "-#, --progress-bar"
1592 This progress bar draws a single line of '#' characters across the screen and
1594 known size, there will be space ship (-=o=-) that moves back and forth but
1597 .IP "--proto-default <protocol>"
1602  curl --proto-default https ftp.mozilla.org
1609 Without this option curl would make a guess based on the host, see \fI--url\fP for
1613 .IP "--proto-redir <protocols>"
1615 \fI--proto\fP are not overridden by this option. See --proto for how protocols are
1620  curl --proto-redir -all,http,https http://example.com
1628 .IP "--proto <protocols>"
1638 .B -
1650 .B \fI--proto\fP -ftps
1653 .B  \fI--proto\fP -all,https,+http
1656 .B \fI--proto\fP =http,https
1667 See also \fI--proto-redir\fP and \fI--proto-default\fP. Added in 7.20.2.
1668 .IP "--proxy-anyauth"
1670 the given HTTP proxy. This might cause an extra request/response round-trip.
1672 See also \fI-x, --proxy\fP and \fI--proxy-basic\fP and \fI--proxy-digest\fP. Added in 7.13.2.
1673 .IP "--proxy-basic"
1675 proxy. Use \fI--basic\fP for enabling HTTP Basic with a remote host. Basic is the
1678 See also \fI-x, --proxy\fP and \fI--proxy-anyauth\fP and \fI--proxy-digest\fP.
1679 .IP "--proxy-cacert <file>"
1680 Same as \fI--cacert\fP but used in HTTPS proxy context.
1682 See also \fI--proxy-capath\fP and \fI--cacert\fP and \fI--capath\fP and \fI-x, --proxy\fP. Added in…
1683 .IP "--proxy-capath <dir>"
1684 Same as \fI--capath\fP but used in HTTPS proxy context.
1686 See also \fI--proxy-cacert\fP and \fI-x, --proxy\fP and \fI--capath\fP. Added in 7.52.0.
1687 .IP "--proxy-cert-type <type>"
1688 Same as \fI--cert-type\fP but used in HTTPS proxy context.
1691 .IP "--proxy-cert <cert[:passwd]>"
1692 Same as \fI-E, --cert\fP but used in HTTPS proxy context.
1695 .IP "--proxy-ciphers <list>"
1696 Same as \fI--ciphers\fP but used in HTTPS proxy context.
1699 .IP "--proxy-crlfile <file>"
1700 Same as \fI--crlfile\fP but used in HTTPS proxy context.
1703 .IP "--proxy-digest"
1705 proxy. Use \fI--digest\fP for enabling HTTP Digest with a remote host.
1707 See also \fI-x, --proxy\fP and \fI--proxy-anyauth\fP and \fI--proxy-basic\fP.
1708 .IP "--proxy-header <header/@file>"
1710 specify any number of extra headers. This is the equivalent option to \fI-H, --header\fP
1715 end-of-line marker, you should thus \fBnot\fP add that as a part of the header
1723 then adds a header for each line in the input file. Using @- will make curl
1729 .IP "--proxy-insecure"
1730 Same as \fI-k, --insecure\fP but used in HTTPS proxy context.
1733 .IP "--proxy-key-type <type>"
1734 Same as \fI--key-type\fP but used in HTTPS proxy context.
1737 .IP "--proxy-key <key>"
1738 Same as \fI--key\fP but used in HTTPS proxy context.
1739 .IP "--proxy-negotiate"
1741 with the given proxy. Use \fI--negotiate\fP for enabling HTTP Negotiate (SPNEGO)
1744 See also \fI--proxy-anyauth\fP and \fI--proxy-basic\fP. Added in 7.17.1.
1745 .IP "--proxy-ntlm"
1747 proxy. Use \fI--ntlm\fP for enabling NTLM with a remote host.
1749 See also \fI--proxy-negotiate\fP and \fI--proxy-anyauth\fP.
1750 .IP "--proxy-pass <phrase>"
1751 Same as \fI--pass\fP but used in HTTPS proxy context.
1754 .IP "--proxy-pinnedpubkey <hashes>"
1756 proxy. This can be a path to a file which contains a single public key in PEM
1766 .IP "--proxy-service-name <name>"
1770 .IP "--proxy-ssl-allow-beast"
1771 Same as \fI--ssl-allow-beast\fP but used in HTTPS proxy context.
1774 .IP "--proxy-tls13-ciphers <ciphersuite list>"
1779  https://curl.haxx.se/docs/ssl-ciphers.html
1782 .IP "--proxy-tlsauthtype <type>"
1783 Same as \fI--tlsauthtype\fP but used in HTTPS proxy context.
1786 .IP "--proxy-tlspassword <string>"
1787 Same as \fI--tlspassword\fP but used in HTTPS proxy context.
1790 .IP "--proxy-tlsuser <name>"
1791 Same as \fI--tlsuser\fP but used in HTTPS proxy context.
1794 .IP "--proxy-tlsv1"
1795 Same as \fI-1, --tlsv1\fP but used in HTTPS proxy context.
1798 .IP "-U, --proxy-user <user:password>"
1801 If you use a Windows SSPI-enabled curl binary and do either Negotiate or NTLM
1803 from your environment by specifying a single colon with this option: "-U :".
1812 .IP "-x, --proxy [protocol://]host[:port]"
1836 one with the \fI-p, --proxytunnel\fP option.
1847 .IP "--proxy1.0 <host[:port]>"
1851 The only difference between this and the HTTP proxy option \fI-x, --proxy\fP, is that
1854 .IP "-p, --proxytunnel"
1855 When an HTTP proxy is used \fI-x, --proxy\fP, this option will make curl tunnel through
1861 use \fI--suppress-connect-headers\fP.
1863 See also \fI-x, --proxy\fP.
1864 .IP "--pubkey <key>"
1874 .IP "-Q, --quote"
1879 transfer, prefix them with a dash '-'.  To make commands be sent after curl
1894 shell-style to embed spaces or special characters.  Following is the list of
1915 .IP "rename source target"
1917 operand to the destination path named by the target operand.
1926 .IP "--random-file <file>"
1929 also the \fI--egd-file\fP option.
1930 .IP "-r, --range <range>"
1935 .B 0-499
1938 .B 500-999
1941 .B -500
1944 .B 9500-
1947 .B 0-0,-1
1950 .B 100-199,500-599
1951 specifies two separate 100-byte ranges(*) (HTTP)
1957 Only digit characters (0-9) are valid in the 'start' and 'stop' fields of the
1958 \&'start-stop' range syntax. If a non-digit character is given in the range,
1966 FTP and SFTP range downloads only support the simple 'start-stop' syntax
1971 .IP "--raw"
1976 .IP "-e, --referer <URL>"
1978 with the \fI-H, --header\fP flag of course.  When used with \fI-L, --location\fP you can append
1979 ";auto" to the \fI-e, --referer\fP URL to make curl automatically set the previous URL
1981 even if you don't set an initial \fI-e, --referer\fP.
1985 See also \fI-A, --user-agent\fP and \fI-H, --header\fP.
1986 .IP "-J, --remote-header-name"
1987 (HTTP) This option tells the \fI-O, --remote-name\fP option to use the server-specified
1988 Content-Disposition filename instead of extracting a filename from the URL.
1995 There's no attempt to decode %-sequences (yet) in the provided file name, so
2001 .IP "--remote-name-all"
2003 if \fI-O, --remote-name\fP were used for each one. So if you want to disable that for a
2004 specific URL after \fI--remote-name-all\fP has been used, you must use "-o -" or
2005 --no-remote-name.
2008 .IP "-O, --remote-name"
2018 server to be able to choose the file name refer to \fI-J, --remote-header-name\fP which
2023 encoded parts of the name, they will end up as-is as file name.
2026 .IP "-R, --remote-time"
2030 .IP "--request-target"
2031 (HTTP) Tells curl to use an alternative "target" (path) instead of using the path as
2037 .IP "-X, --request <command>"
2050 request, using -X HEAD will not suffice. You need to use the \fI-I, --head\fP option.
2052 The method string you set with \fI-X, --request\fP will be used for all requests, which
2053 if you for example use \fI-L, --location\fP may cause unintended side-effects when curl
2054 doesn't change request method according to the HTTP 30x response codes - and
2072 .IP "--resolve <host:port:address[,address]...>"
2082 port pair to the specified address. Wildcard is resolved last so any \fI--resolve\fP
2085 The provided address set by this option will be used even if \fI-4, --ipv4\fP or \fI-6, --ipv6\fP
2097 .IP "--retry-connrefused"
2099 error too for \fI--retry\fP. This option is used together with --retry.
2102 .IP "--retry-delay <seconds>"
2105 between retries). This option is only interesting if \fI--retry\fP is also
2111 .IP "--retry-max-time <seconds>"
2113 done as usual (see \fI--retry\fP) as long as the timer hasn't reached this given
2116 limit a single request\'s maximum time, use \fI-m, --max-time\fP.  Set this option to
2122 .IP "--retry <num>"
2131 using \fI--retry-delay\fP you disable this exponential backoff algorithm. See also
2132 \fI--retry-max-time\fP to limit the total time allowed for retries.
2137 .IP "--sasl-ir"
2141 .IP "--service-name <name>"
2144 Examples: \fI--negotiate\fP \fI--service-name\fP sockd would use sockd/server-name.
2147 .IP "-S, --show-error"
2148 When used with \fI-s, --silent\fP, it makes curl show an error message if it fails.
2149 .IP "-s, --silent"
2154 Use \fI-S, --show-error\fP in addition to this option to disable progress meter but
2157 See also \fI-v, --verbose\fP and \fI--stderr\fP.
2158 .IP "--socks4 <host[:port]>"
2162 This option overrides any previous use of \fI-x, --proxy\fP, as they are mutually
2166 with \fI-x, --proxy\fP using a socks4:// protocol prefix.
2168 Since 7.52.0, \fI--preproxy\fP can be used to specify a SOCKS proxy at the same time
2169 \fI-x, --proxy\fP is used with an HTTP/HTTPS proxy. In such a case curl first connects to
2175 .IP "--socks4a <host[:port]>"
2179 This option overrides any previous use of \fI-x, --proxy\fP, as they are mutually
2183 with \fI-x, --proxy\fP using a socks4a:// protocol prefix.
2185 Since 7.52.0, \fI--preproxy\fP can be used to specify a SOCKS proxy at the same time
2186 \fI-x, --proxy\fP is used with an HTTP/HTTPS proxy. In such a case curl first connects to
2192 .IP "--socks5-basic"
2195 \fI--socks5-gssapi\fP to force GSS-API authentication to SOCKS5 proxies.
2198 .IP "--socks5-gssapi-nec"
2199 As part of the GSS-API negotiation a protection mode is negotiated. RFC 1961
2201 implementation does not.  The option \fI--socks5-gssapi-nec\fP allows the
2205 .IP "--socks5-gssapi-service <name>"
2206 The default service name for a socks server is rcmd/server-fqdn. This option
2209 Examples: \fI--socks5\fP proxy-name \fI--socks5-gssapi-service\fP sockd would use
2210 sockd/proxy-name \fI--socks5\fP proxy-name \fI--socks5-gssapi-service\fP sockd/real-name
2211 would use sockd/real-name for cases where the proxy-name does not match the
2215 .IP "--socks5-gssapi"
2216 Tells curl to use GSS-API authentication when connecting to a SOCKS5 proxy.
2217 The GSS-API authentication is enabled by default (if curl is compiled with
2218 GSS-API support).  Use \fI--socks5-basic\fP to force username/password authentication
2222 .IP "--socks5-hostname <host[:port]>"
2226 This option overrides any previous use of \fI-x, --proxy\fP, as they are mutually
2230 hostname proxy with \fI-x, --proxy\fP using a socks5h:// protocol prefix.
2232 Since 7.52.0, \fI--preproxy\fP can be used to specify a SOCKS proxy at the same time
2233 \fI-x, --proxy\fP is used with an HTTP/HTTPS proxy. In such a case curl first connects to
2239 .IP "--socks5 <host[:port]>"
2240 Use the specified SOCKS5 proxy - but resolve the host name locally. If the
2243 This option overrides any previous use of \fI-x, --proxy\fP, as they are mutually
2247 with \fI-x, --proxy\fP using a socks5:// protocol prefix.
2249 Since 7.52.0, \fI--preproxy\fP can be used to specify a SOCKS proxy at the same time
2250 \fI-x, --proxy\fP is used with an HTTP/HTTPS proxy. In such a case curl first connects to
2255 This option (as well as \fI--socks4\fP) does not work with IPV6, FTPS or LDAP.
2258 .IP "-Y, --speed-limit <speed>"
2260 speed-time seconds it gets aborted. speed-time is set with \fI-y, --speed-time\fP and is
2264 .IP "-y, --speed-time <seconds>"
2265 If a download is slower than speed-limit bytes per second during a speed-time
2266 period, the download gets aborted. If speed-time is used, the default
2267 speed-limit will be 1 unless set with \fI-Y, --speed-limit\fP.
2270 this is a concern for you, try the \fI--connect-timeout\fP option.
2273 .IP "--ssl-allow-beast"
2281 .IP "--ssl-no-revoke"
2287 .IP "--ssl-reqd"
2291 This option was formerly known as --ftp-ssl-reqd.
2294 .IP "--ssl"
2296 Try to use SSL/TLS for the connection.  Reverts to a non-secure connection if
2297 the server doesn't support SSL/TLS.  See also \fI--ftp-ssl-control\fP and \fI--ssl-reqd\fP
2300 This option was formerly known as --ftp-ssl (Added in 7.11.0). That option
2304 .IP "-2, --sslv2"
2309 …--http1.1\fP and \fI--http2\fP. \fI-2, --sslv2\fP requires that the underlying libcurl was built t…
2310 .IP "-3, --sslv3"
2315 …--http1.1\fP and \fI--http2\fP. \fI-3, --sslv3\fP requires that the underlying libcurl was built t…
2316 .IP "--stderr"
2318 is a plain '-', it is instead written to stdout.
2322 See also \fI-v, --verbose\fP and \fI-s, --silent\fP.
2323 .IP "--styled-output"
2325 terminal. Use --no-styled-output to switch them off.
2328 .IP "--suppress-connect-headers"
2329 When \fI-p, --proxytunnel\fP is used and a CONNECT request is made don't output proxy
2330 CONNECT response headers. This option is meant to be used with \fI-D, --dump-header\fP or
2331 \fI-i, --include\fP which are used to show protocol headers in the output. It has no
2332 effect on debug options such as \fI-v, --verbose\fP or \fI--trace\fP, or any statistics.
2334 See also \fI-D, --dump-header\fP and \fI-i, --include\fP and \fI-p, --proxytunnel\fP.
2335 .IP "--tcp-fastopen"
2339 .IP "--tcp-nodelay"
2347 .IP "-t, --telnet-option <opt=val>"
2355 .IP "--tftp-blksize <value>"
2363 .IP "--tftp-no-options"
2367 or properly implement TFTP options. When this option is used \fI--tftp-blksize\fP is
2371 .IP "-z, --time-cond <time>"
2378 Start the date expression with a dash (-) to make it request for a document
2383 .IP "--tls-max <VERSION>"
2400 See also \fI--tlsv1.0\fP and \fI--tlsv1.1\fP and \fI--tlsv1.2\fP and \fI--tlsv1.3\fP. \fI--tls-max\…
2401 .IP "--tls13-ciphers <list of TLS 1.3 ciphersuites>"
2406  https://curl.haxx.se/docs/ssl-ciphers.html
2409 .IP "--tlsauthtype <type>"
2411 for TLS-SRP (RFC 5054). If \fI--tlsuser\fP and \fI--tlspassword\fP are specified but
2412 \fI--tlsauthtype\fP is not, then this option defaults to "SRP".  This option works
2413 only if the underlying libcurl is built with TLS-SRP support, which requires
2414 OpenSSL or GnuTLS with TLS-SRP support.
2417 .IP "--tlspassword"
2419 \fI--tlsauthtype\fP. Requires that \fI--tlsuser\fP also be set.
2422 .IP "--tlsuser <name>"
2424 \fI--tlsauthtype\fP. Requires that \fI--tlspassword\fP also is set.
2427 .IP "--tlsv1.0"
2431 .IP "--tlsv1.1"
2435 .IP "--tlsv1.2"
2439 .IP "--tlsv1.3"
2447 .IP "-1, --tlsv1"
2451 …--http1.1\fP and \fI--http2\fP. \fI-1, --tlsv1\fP requires that the underlying libcurl was built t…
2452 .IP "--tr-encoding"
2453 (HTTP) Request a compressed Transfer-Encoding response using one of the algorithms
2457 .IP "--trace-ascii <file>"
2459 descriptive information, to the given output file. Use "-" as filename to have
2462 This is very similar to \fI--trace\fP, but leaves out the hex part and only shows
2468 This option overrides \fI--trace\fP and \fI-v, --verbose\fP.
2469 .IP "--trace-time"
2473 .IP "--trace <file>"
2475 descriptive information, to the given output file. Use "-" as filename to have
2481 This option overrides \fI-v, --verbose\fP and \fI--trace-ascii\fP.
2482 .IP "--unix-socket <path>"
2486 .IP "-T, --upload-file <file>"
2494 Use the file name "-" (a single dash) to use stdin instead of a given file.
2495 Alternately, the file name "." (a single period) may be specified instead
2496 of "-" to use stdin in non-blocking mode to allow reading server output
2499 You can specify one \fI-T, --upload-file\fP for each URL on the command line. Each
2500 \fI-T, --upload-file\fP + URL pair specifies what to upload and to where. curl also
2501 supports "globbing" of the \fI-T, --upload-file\fP argument, meaning that you can upload
2502 multiple files to a single URL by using the same URL globbing style supported
2505  curl --upload-file "{file1,file2}" http://www.example.com
2509  curl -T "img[1-1000].png" ftp://ftp.example.com/upload/
2515 .IP "--url <url>"
2520 then curl will make a guess based on the host. If the outermost sub-domain
2523 setting a default protocol, see \fI--proto-default\fP for details.
2526 written, use the \fI-o, --output\fP or the \fI-O, --remote-name\fP options.
2527 .IP "-B, --use-ascii"
2531 .IP "-A, --user-agent <name>"
2533 Specify the User-Agent string to send to the HTTP server. To encode blanks in
2534 the string, surround the string with single quote marks. This header can also
2535 be set with the \fI-H, --header\fP or the \fI--proxy-header\fP options.
2538 .IP "-u, --user <user:password>"
2540 \fI-n, --netrc\fP and \fI--netrc-optional\fP.
2560 without the domain, if there is a single domain and forest in your setup
2563 To specify the domain name use either Down-Level Logon Name or UPN (User
2567 If you use a Windows SSPI-enabled curl binary and perform Kerberos V5,
2569 the user name and password from your environment by specifying a single colon
2570 with this option: "-u :".
2573 .IP "-v, --verbose"
2580 If you only want HTTP headers in the output, \fI-i, --include\fP might be the option
2584 \fI--trace\fP or \fI--trace-ascii\fP instead.
2586 Use \fI-s, --silent\fP to make curl really quiet.
2588 See also \fI-i, --include\fP. This option overrides \fI--trace\fP and \fI--trace-ascii\fP.
2589 .IP "-V, --version"
2613 This curl uses a libcurl built with Debug. This enables more error-tracking
2614 and memory debugging etc. For curl-developers only!
2617 done using either the c-ares or the threaded resolver backends.
2623 This curl supports IDN - international domain names.
2624 .IP "GSS-API"
2625 GSS-API is supported.
2628 .IP "TLS-SRP"
2631 HTTP/2 support has been built-in.
2634 .IP "HTTPS-proxy"
2646 .IP "-w, --write-out <format>"
2651 format from stdin you write "@-".
2663 The %-symbol is a special symbol in the win32-environment, where all
2670 The Content-Type of the requested document, if there was any.
2674 is told to write to a file with the \fI-O, --remote-name\fP or \fI-o, --output\fP
2675 option. It's most useful in combination with the \fI-J, --remote-header-name\fP
2695 The IP address of the local end of the most recently done connection - can be
2696 either IPv4 or IPv6 (Added in 7.29.0)
2712 When an HTTP request was made without \fI-L, --location\fP to follow redirects (or when
2713 --max-redir is met), this variable will show the actual URL a redirect
2717 The remote IP address of the most recently done connection - can be either
2718 IPv4 or IPv6 (Added in 7.29.0)
2751 From this point on, the \fI-w, --write-out\fP output will be written to standard
2755 From this point on, the \fI-w, --write-out\fP output will be written to standard output.
2773 about to begin. This includes all pre-transfer commands and negotiations that
2796 .IP "--xattr"
2805 Default config file, see \fI-K, --config\fP for details.
2812 the \fI-x, --proxy\fP option.
2818 .IP "[url-protocol]_PROXY [protocol://]<host>[:port]"
2819 Sets the proxy server to use for [url-protocol], where the protocol is a
2823 Sets the proxy server to use if no protocol-specific proxy is set.
2824 .IP "NO_PROXY <comma-separated list of hosts/domains>"
2830 the \fI-x, --proxy\fP option. That is
2831 .B NO_PROXY=direct.example.com curl -x http://proxy.example.com
2833 accesses the target URL directly, and
2834 .B NO_PROXY=direct.example.com curl -x http://proxy.example.com
2836 accesses the target URL through the proxy.
2854 Makes it the equivalent of \fI--socks4\fP
2856 Makes it the equivalent of \fI--socks4a\fP
2858 Makes it the equivalent of \fI--socks5\fP
2860 Makes it the equivalent of \fI--socks5-hostname\fP
2873 enabled or was explicitly disabled at build-time. To make curl able to do
2899 FTP weird 227 format. Curl couldn't parse the 227-line the server sent.
2901 FTP can't get host. Couldn't resolve the host IP we got in the 227-line.
2918 appears if \fI-f, --fail\fP is used.
2929 Operation timeout. The specified time-out period was reached according to the
2940 HTTP post error. Internal post-request generation error.