Lines Matching +full:ipv4 +full:- +full:single +full:- +full:target

8 .\" * Copyright (C) 1998 - 2020, Daniel Stenberg, <daniel@haxx.se>, et al.
28 curl \- transfer a URL
44 curl is powered by libcurl for all transfer-related features. See
47 The URL syntax is protocol-dependent. You'll find a detailed description in
57   "ftp://ftp.example.com/file[1-100].txt"
59   "ftp://ftp.example.com/file[001-100].txt"    (with leading zeros)
61   "ftp://ftp.example.com/file[a-z].txt"
66   "http://example.com/archive[1996-1999]/vol[1-4]/part{a,b,c}.html"
75   "http://example.com/file[1-100:10].txt"
77   "http://example.com/file[a-z:2].txt"
91 based on often-used host name prefixes. For example, for host names starting
98 curl will attempt to re-use connections for multiple file transfers, so that
101 specified on a single command line and cannot be used between separate curl
165 redirect the response output to a file, using shell redirect (>), \fI-o, --output\fP or
171 If you prefer a progress "bar" instead of the regular meter, \fI-#, --progress-bar\fP is
173 \fI-s, --silent\fP option.
178 The short "single-dash" form of the options, -d for example, may be used with
180 separator. The long "double-dash" form, \fI-d, --data\fP for example, requires a space
185 options -O, -L and -v at once as -OLv.
187 In general, all boolean options are enabled with --\fBoption\fP and yet again
188 disabled with --\fBno-\fPoption. That is, you use the exact same option name
189 but prefix it with "no-". However, in this list we mostly only list and show
190 the --option version of them. (This concept with --no options was added in
193 .IP "--abstract-unix-socket <path>"
199 .IP "--alt-svc <file name>"
202 This option enables the alt-svc parser in curl. If the file name points to an
203 existing alt-svc cache file, that will be used. After a completed transfer,
213 .IP "--anyauth"
216 request and checking the response-headers, thus possibly inducing an extra
217 network round-trip. This is used instead of setting a specific authentication
218 method, which you can do with \fI--basic\fP, \fI--digest\fP, \fI--ntlm\fP, and \fI--negotiate\fP.
220 Using \fI--anyauth\fP is not recommended if you do uploads from stdin, since it may
225 Used together with \fI-u, --user\fP.
227 See also \fI--proxy-anyauth\fP, \fI--basic\fP and \fI--digest\fP.
228 .IP "-a, --append"
229 (FTP SFTP) When used in an upload, this makes curl append to the target file instead of
232 .IP "--basic"
236 \fI--ntlm\fP, \fI--digest\fP, or \fI--negotiate\fP).
238 Used together with \fI-u, --user\fP.
240 See also \fI--proxy-basic\fP.
241 .IP "--cacert <file>"
252 \'curl-ca-bundle.crt\', either in the same directory as curl.exe, or in the
270 .IP "--capath <dir>"
275 c_rehash utility supplied with OpenSSL. Using \fI--capath\fP can allow
276 OpenSSL-powered curl to make SSL-connections much more efficiently than using
277 \fI--cacert\fP if the --cacert file contains many CA certificates.
281 .IP "--cert-status"
292 .IP "--cert-type <type>"
298 See also \fI-E, --cert\fP, \fI--key\fP and \fI--key-type\fP.
299 .IP "-E, --cert <certificate[:password]>"
301 with HTTPS, FTPS or another SSL-based protocol. The certificate must be in
305 private key and the client certificate concatenated! See \fI-E, --cert\fP and \fI--key\fP to
321 PKCS#11 URI. If a PKCS#11 URI is provided, then the \fI--engine\fP option will be set
322 as "pkcs11" if none was provided and the \fI--cert-type\fP option will be set as
327 system or user keychain, or the path to a PKCS#12-encoded certificate and
337 usually a SHA-1 hex string which you can see in certificate details. Following
344 See also \fI--cert-type\fP, \fI--key\fP and \fI--key-type\fP.
345 .IP "--ciphers <list of ciphers>"
349  https://curl.haxx.se/docs/ssl-ciphers.html
352 .IP "--compressed-ssh"
353 (SCP SFTP) Enables built-in SSH compression.
357 .IP "--compressed"
363 .IP "-K, --config <file>"
383 Specify the filename to \fI-K, --config\fP as '-' to make curl read the file from stdin.
386 it using the \fI--url\fP option, and not by simply writing the URL on its own
391 When curl is invoked, it (unless \fI-q, --disable\fP is used) checks for a default
401 4) Non-windows: use getpwuid to find the home directory
408 in the same dir the curl executable is placed. On Unix-like systems, it will
412 # --- Example file ---
416 user-agent = "superagent/1.0"
422 # --- End of example file ---
426 .IP "--connect-timeout <seconds>"
429 will continue - if not it will exit.  Since version 7.32.0, this option
434 See also \fI-m, --max-time\fP.
435 .IP "--connect-to <HOST1:PORT1:HOST2:PORT2>"
452 See also \fI--resolve\fP and \fI-H, --header\fP. Added in 7.49.0.
453 .IP "-C, --continue-at <offset>"
459 Use "-C -" to tell curl to automatically find out where/how to resume the
464 See also \fI-r, --range\fP.
465 .IP "-c, --cookie-jar <filename>"
467 operation. Curl writes all cookies from its in-memory cookie storage to the
470 you set the file name to a single dash, "-", the cookies will be written to
474 record and use cookies. Another way to activate it is to use the \fI-b, --cookie\fP
478 won't fail or even report an error clearly. Using \fI-v, --verbose\fP will get a warning
484 .IP "-b, --cookie <data|filename>"
486 the data previously received from the server in a "Set-Cookie:" line.  The
492 you're using this in combination with the \fI-L, --location\fP option or do multiple URL
493 transfers on the same invoke. If the file name is exactly a minus ("-"), curl
497 (Set-Cookie style) or the Netscape/Mozilla cookie file format.
499 The file specified with \fI-b, --cookie\fP is only used as input. No cookies will be
500 written to the file. To store cookies, use the \fI-c, --cookie-jar\fP option.
503 occur.  If you use the NAME1=VALUE1; format, or in a file use the Set-Cookie
505 (even after redirects are followed) and cannot be modified by a server-set
508 what you intended.  To address these issues set a domain in Set-Cookie (doing
514 cookies back to a file, so using both \fI-b, --cookie\fP and \fI-c, --cookie-jar\fP in the same
516 .IP "--create-dirs"
517 When used in conjunction with the \fI-o, --output\fP option, curl will create the
519 mentioned with the \fI-o, --output\fP option, nothing else. If the --output file name
524 To create remote directories when using FTP or SFTP, try \fI--ftp-create-dirs\fP.
525 .IP "--crlf"
529 .IP "--crlfile <file>"
536 .IP "--curves <algorithm list>"
539 them with ":" (e.g.  "X25519:P-521").  The parameter is available identically
542 \fI--curves\fP allows a OpenSSL powered curl to make SSL-connections with exactly
550 .IP "--data-ascii <data>"
551 (HTTP) This is just an alias for \fI-d, --data\fP.
552 .IP "--data-binary <data>"
556 is posted in a similar manner as \fI-d, --data\fP does, except that newlines and
559 Like \fI-d, --data\fP the default content-type sent to the server is
560 application/x-www-form-urlencoded. If you want the data to be treated as
561 arbitrary binary data by the server then set the content-type to octet-stream:
562 -H "Content-Type: application/octet-stream".
565 data as described in \fI-d, --data\fP.
566 .IP "--data-raw <data>"
567 (HTTP) This posts data similarly to \fI-d, --data\fP but without the special
570 See also \fI-d, --data\fP. Added in 7.43.0.
571 .IP "--data-urlencode <data>"
572 (HTTP) This posts data, similar to the other \fI-d, --data\fP options with the exception
573 that this performs URL-encoding.
575 To be CGI-compliant, the <data> part should begin with a \fIname\fP followed
580 This will make curl URL-encode the content and pass that on. Just be careful
584 This will make curl URL-encode the content and pass that on. The preceding =
587 This will make curl URL-encode the content part and pass that on. Note that
588 the name part is expected to be URL-encoded already.
591 URL-encode that data and pass it on in the POST.
594 URL-encode that data and pass it on in the POST. The name part gets an equal
595 sign appended, resulting in \fIname=urlencoded-file-content\fP. Note that the
596 name is expected to be URL-encoded already.
599 See also \fI-d, --data\fP and \fI--data-raw\fP. Added in 7.18.0.
600 .IP "-d, --data <data>"
604 content-type application/x-www-form-urlencoded.  Compare to \fI-F, --form\fP.
606 \fI--data-raw\fP is almost the same but does not have a special interpretation of
608 \fI--data-binary\fP option.  To URL-encode the value of a form field you may use
609 \fI--data-urlencode\fP.
613 &-symbol. Thus, using '-d name=daniel -d skill=lousy' would generate a post
617 read the data from, or - if you want curl to read the data from stdin. Posting
618 data from a file named \&'foobar' would thus be done with \fI-d, --data\fP @foobar. When
619 \fI-d, --data\fP is told to read from a file like that, carriage returns and newlines
621 interpretation use \fI--data-raw\fP instead.
623 …o \fI--data-binary\fP, \fI--data-urlencode\fP and \fI--data-raw\fP. This option overrides \fI-F, -…
624 .IP "--delegation <LEVEL>"
631 Delegates if and only if the OK-AS-DELEGATE flag is set in the Kerberos
636 .IP "--digest"
639 combination with the normal \fI-u, --user\fP option to set user name and password.
643 See also \fI-u, --user\fP, \fI--proxy-digest\fP and \fI--anyauth\fP. This option overrides \fI--bas…
644 .IP "--disable-eprt"
652 --eprt can be used to explicitly enable EPRT again and --no-eprt is an alias
653 for \fI--disable-eprt\fP.
659 passive mode you need to not use \fI-P, --ftp-port\fP or force it with \fI--ftp-pasv\fP.
660 .IP "--disable-epsv"
665 --epsv can be used to explicitly enable EPSV again and --no-epsv is an alias
666 for \fI--disable-epsv\fP.
672 active mode you need to use \fI-P, --ftp-port\fP.
673 .IP "-q, --disable"
675 file will not be read and used. See the \fI-K, --config\fP for details on the default
677 .IP "--disallow-username-in-url"
680 See also \fI--proto\fP. Added in 7.61.0.
681 .IP "--dns-interface <interface>"
683 counterpart to \fI--interface\fP (which does not affect DNS). The supplied string
686 See also \fI--dns-ipv4-addr\fP and \fI--dns-ipv6-addr\fP. \fI--dns-interface\fP requires that the u…
687 .IP "--dns-ipv4-addr <address>"
688 (DNS) Tell curl to bind to <ip-address> when making IPv4 DNS requests, so that
690 single IPv4 address.
692 See also \fI--dns-interface\fP and \fI--dns-ipv6-addr\fP. \fI--dns-ipv4-addr\fP requires that the u…
693 .IP "--dns-ipv6-addr <address>"
694 (DNS) Tell curl to bind to <ip-address> when making IPv6 DNS requests, so that
696 single IPv6 address.
698 See also \fI--dns-interface\fP and \fI--dns-ipv4-addr\fP. \fI--dns-ipv6-addr\fP requires that the u…
699 .IP "--dns-servers <addresses>"
702 may also optionally be given as \fI:<port-number>\fP after each IP
705 \fI--dns-servers\fP requires that the underlying libcurl was built to support c-ares. Added in 7.33…
706 .IP "--doh-url <URL>"
707 (all) Specifies which DNS-over-HTTPS (DOH) server to use to resolve hostnames,
713 .IP "-D, --dump-header <filename>"
718 curl invocation by using the \fI-b, --cookie\fP option! The \fI-c, --cookie-jar\fP option is a
728 See also \fI-o, --output\fP.
729 .IP "--egd-file <file>"
733 See also \fI--random-file\fP.
734 .IP "--engine <name>"
735 (TLS) Select the OpenSSL crypto engine to use for cipher operations. Use \fI--engine\fP
736 list to print a list of build-time supported engines. Note that not all (or
737 none) of the engines may be available at run-time.
738 .IP "--etag-compare <file>"
740 ETag read from the given file by sending a custom If-None-Match
743 For correct results, make sure that specified file contains only a single
746 Use the option \fI--etag-save\fP to first save the ETag from a response, and
753 .IP "--etag-save <file>"
766 .IP "--expect100-timeout <seconds>"
767 (HTTP) Maximum time in seconds that you allow curl to wait for a 100-continue
768 response when curl emits an Expects: 100-continue header in its request. By
772 See also \fI--connect-timeout\fP. Added in 7.47.0.
773 .IP "--fail-early"
786 This option is global and does not need to be specified for each use of \fI-:, --next\fP.
788 This option does not imply \fI-f, --fail\fP, which causes transfers to fail due to the
789 server's HTTP status code. You can combine the two options, however note \fI-f, --fail\fP
790 is not global and is therefore contained by \fI-:, --next\fP.
793 .IP "-f, --fail"
800 This method is not fail-safe and there are occasions where non-successful
803 .IP "--false-start"
813 .IP "--form-string <name=string>"
814 (HTTP SMTP IMAP) Similar to \fI-F, --form\fP except that the value string for the named parameter i…
816 the value have no special meaning. Use this in preference to \fI-F, --form\fP if
818 \&'@' or \&'<' features of \fI-F, --form\fP.
820 See also \fI-F, --form\fP.
821 .IP "-F, --form <name=content>"
822 (HTTP SMTP IMAP) For HTTP protocol family, this lets curl emulate a filled-in form in which a
824 Content-Type multipart/form-data according to RFC 2388.
836 Tell curl to read content from stdin instead of a file by using - as
839 possible resend.  Defining a part's data from a named non-regular file (such
846 form-field to which the file portrait.jpg will be the input:
848  curl -F profile=@portrait.jpg https://example.com/upload.cgi
852  curl -F name=John -F shoesize=11 https://example.com/
857  curl -F "story=<hugefile.txt" https://example.com/
859 You can also tell curl what Content-Type to use by using 'type=', in a manner
862  curl -F "web=@index.html;type=text/html" example.com
866  curl -F "name=daniel;type=text/foo" example.com
871  curl -F "file=@localfile;filename=nameinpost" example.com
873 If filename/path contains ',' or ';', it must be quoted by double-quotes like:
875  curl -F "file=@\\"localfile\\";filename=\\"nameinpost\\"" example.com
879  curl -F 'file=@"localfile";filename="nameinpost"' example.com
881 Note that if a filename/path is quoted by double-quotes, any double-quote
884 Quoting must also be applied to non-file data if it contains semicolons,
887  curl -F 'colors="red; green; blue";type=text/x-myapp' example.com
891   curl -F "submit=OK;headers=\\"X-submit-type: OK\\"" example.com
895   curl -F "submit=OK;headers=@headerfile" example.com
901 carriage-returns and trailing spaces are stripped.
906   X-header-1: this is a header
910   X-header-2: this is
917 - name can be omitted: the equal sign is the first character of the argument,
919 - if data starts with '(', this signals to start a new multipart: it can be
922 - a multipart can be terminated with a '=)' argument.
924 Example: the following command sends an SMTP mime e-mail consisting in an
928  curl -F '=(;type=multipart/alternative' \\
930          -F '=plain text message' \\
932          -F '= <body>HTML message</body>;type=text/html' \\
934       -F '=)' -F '=@textfile.txt' ...  smtp://example.com
938 Content-Transfer-Encoding header, \fI7bit\fP that only rejects 8-bit characters
939 with a transfer error, \fIquoted-printable\fP and \fIbase64\fP that encodes
943 Example: send multipart mail with a quoted-printable text message and a
946  curl -F '=text message;encoder=quoted-printable' \\
948       -F '=@localfile;encoder=base64' ... smtp://example.com
954 This option overrides \fI-d, --data\fP and \fI-I, --head\fP and \fI-T, --upload-file\fP.
955 .IP "--ftp-account <data>"
962 .IP "--ftp-alternative-to-user <command>"
969 .IP "--ftp-create-dirs"
974 See also \fI--create-dirs\fP.
975 .IP "--ftp-method <method>"
980 curl does a single CWD operation for each path part in the given URL. For deep
987 curl does one CWD with the full target directory and then operates on the file
993 .IP "--ftp-pasv"
995 behavior, but using this option can be used to override a previous \fI-P, --ftp-port\fP
1000 correct \fI-P, --ftp-port\fP again.
1003 unless \fI--disable-epsv\fP is used.
1005 See also \fI--disable-epsv\fP. Added in 7.11.0.
1006 .IP "-P, --ftp-port <address>"
1019 .IP "-"
1025 use of PORT with \fI--ftp-pasv\fP. Disable the attempt to use the EPRT command
1026 instead of PORT by using \fI--disable-eprt\fP. EPRT is really PORT++.
1028 Since 7.19.5, you can append \&":[start]-[end]\&" to the right of the address,
1030 from a lower to a higher number. A single number works as well, but do note
1033 See also \fI--ftp-pasv\fP and \fI--disable-eprt\fP.
1034 .IP "--ftp-pret"
1036 mainly drftpd, require this non-standard command for directory listings as
1040 .IP "--ftp-skip-pasv-ip"
1043 will re-use the same IP address it already uses for the control
1048 See also \fI--ftp-pasv\fP. Added in 7.14.2.
1049 .IP "--ftp-ssl-ccc-mode <active/passive>"
1055 See also \fI--ftp-ssl-ccc\fP. Added in 7.16.2.
1056 .IP "--ftp-ssl-ccc"
1062 See also \fI--ssl\fP and \fI--ftp-ssl-ccc-mode\fP. Added in 7.16.1.
1063 .IP "--ftp-ssl-control"
1065 authentication, but non-encrypted data transfers for efficiency.  Fails the
1069 .IP "-G, --get"
1070 When used, this option will make all data specified with \fI-d, --data\fP, \fI--data-binary\fP
1071 or \fI--data-urlencode\fP to be used in an HTTP GET request instead of the POST
1075 If used in combination with \fI-I, --head\fP, the POST data will instead be appended to
1081 .IP "-g, --globoff"
1086 .IP "--happy-eyeballs-timeout-ms <milliseconds>"
1087 Happy eyeballs is an algorithm that attempts to connect to both IPv4 and IPv6
1088 addresses for dual-stack hosts, preferring IPv6 first for the number of
1090 a connection attempt is made to the IPv4 address in parallel. The first
1094 "It is RECOMMENDED that connection attempts be paced 150-250 ms apart to
1101 .IP "--haproxy-protocol"
1110 .IP "-I, --head"
1111 (HTTP FTP FILE) Fetch the headers only! HTTP-servers feature the command HEAD which this uses
1114 .IP "-H, --header <header/@file>"
1122 the right side of the colon, as in: -H \&"Host:". If you send the custom
1123 header with no-value then its header must be terminated with a semicolon, such
1124 as \-H \&"X-Custom-Header;" to send "X-Custom-Header:".
1127 end-of-line marker, you should thus \fBnot\fP add that as a part of the header
1132 then adds a header for each line in the input file. Using @- will make curl
1135 See also the \fI-A, --user-agent\fP and \fI-e, --referer\fP options.
1137 Starting in 7.37.0, you need \fI--proxy-header\fP to send custom headers intended
1142  curl -H "X-First-Name: Joe" http://example.com/
1144 \fBWARNING\fP: headers set with this option will be set in all requests - even
1145 after redirects are followed, like when told with \fI-L, --location\fP. This can lead to
1150 .IP "-h, --help <category>"
1157 .IP "--hostpubmd5 <md5>"
1163 .IP "--http0.9"
1167 connect with this to non-HTTP servers and still get a response since curl will
1168 simply transparently downgrade - if allowed.
1171 .IP "-0, --http1.0"
1175 This option overrides \fI--http1.1\fP and \fI--http2\fP.
1176 .IP "--http1.1"
1179 This option overrides \fI-0, --http1.0\fP and \fI--http2\fP. Added in 7.33.0.
1180 .IP "--http2-prior-knowledge"
1181 (HTTP) Tells curl to issue its non-TLS HTTP requests using HTTP/2 without HTTP/1.1
1186 …--http2-prior-knowledge\fP requires that the underlying libcurl was built to support HTTP/2. This …
1187 .IP "--http2"
1190 …--http1.1\fP and \fI--http3\fP. \fI--http2\fP requires that the underlying libcurl was built to su…
1191 .IP "--http3"
1197 redirected via Alt-SVc, but this option allows a user to circumvent that when
1198 you know that the target speaks HTTP/3 on the given host and port.
1203 …--http1.1\fP and \fI--http2\fP. \fI--http3\fP requires that the underlying libcurl was built to su…
1204 .IP "--ignore-content-length"
1205 (FTP HTTP) For HTTP, Ignore the Content-Length header. This is particularly useful for
1206 servers running Apache 1.x, which will report incorrect Content-Length for
1211 .IP "-i, --include"
1216 To view the request headers, consider the \fI-v, --verbose\fP option.
1218 See also \fI-v, --verbose\fP.
1219 .IP "-k, --insecure"
1231 See also \fI--proxy-insecure\fP and \fI--cacert\fP.
1232 .IP "--interface <name>"
1237  curl --interface eth0:1 https://www.example.com/
1245 See also \fI--dns-interface\fP.
1246 .IP "-4, --ipv4"
1247 This option tells curl to resolve names to IPv4 addresses only, and not for
1250 See also \fI--http1.1\fP and \fI--http2\fP. This option overrides \fI-6, --ipv6\fP.
1251 .IP "-6, --ipv6"
1253 example try IPv4.
1255 See also \fI--http1.1\fP and \fI--http2\fP. This option overrides \fI-4, --ipv4\fP.
1256 .IP "-j, --junk-session-cookies"
1262 See also \fI-b, --cookie\fP and \fI-c, --cookie-jar\fP.
1263 .IP "--keepalive-time <seconds>"
1267 TCP_KEEPINTVL socket options (meaning Linux, recent AIX, HP-UX and more). This
1268 option has no effect if \fI--no-keepalive\fP is used.
1274 .IP "--key-type <type>"
1275 (TLS) Private key file type. Specify which type your \fI--key\fP provided private key
1279 .IP "--key <key>"
1287 PKCS#11 URI. If a PKCS#11 URI is provided, then the \fI--engine\fP option will be set
1288 as "pkcs11" if none was provided and the \fI--key-type\fP option will be set as
1292 .IP "--krb <level>"
1299 \fI--krb\fP requires that the underlying libcurl was built to support Kerberos.
1300 .IP "--libcurl <file>"
1302 libcurl-using C source code written to the file that does the equivalent
1303 of what your command-line operation does!
1309 .IP "--limit-rate <speed>"
1310 Specify the maximum transfer rate you want curl to use - for both downloads
1319 If you also use the \fI-Y, --speed-limit\fP option, that option will take precedence and
1320 might cripple the rate-limiting slightly, to help keeping the speed-limit
1324 .IP "-l, --list-only"
1326 When listing an FTP directory, this switch forces a name-only view. This is
1327 especially useful if the user wants to machine-parse the contents of an FTP
1333 include sub-directories and symbolic links.
1340 Note: When combined with \fI-X, --request\fP, this option can be used to send an UIDL
1345 .IP "--local-port <num/range>"
1346 Set a preferred single number or range (FROM-TO) of local port numbers to use
1352 .IP "--location-trusted"
1353 (HTTP) Like \fI-L, --location\fP, but will allow sending the name + password to all hosts that
1358 See also \fI-u, --user\fP.
1359 .IP "-L, --location"
1363 \fI-i, --include\fP or \fI-I, --head\fP, headers from all requested pages will be shown. When
1366 intercept the user+password. See also \fI--location-trusted\fP on how to change
1368 \fI--max-redirs\fP option.
1372 response code was any other 3xx code, curl will re-send the following request
1376 using the dedicated options for that: \fI--post301\fP, \fI--post302\fP and \fI--post303\fP.
1378 The method set with \fI-X, --request\fP overrides the method curl would otherwise select
1380 .IP "--login-options <options>"
1386 RFC 2384, RFC 5092 and IETF draft draft-earhart-url-smtp-00.txt
1391 .IP "--mail-auth <address>"
1392 (SMTP) Specify a single address. This will be used to specify the authentication
1396 See also \fI--mail-rcpt\fP and \fI--mail-from\fP. Added in 7.25.0.
1397 .IP "--mail-from <address>"
1398 (SMTP) Specify a single address that the given mail should get sent from.
1400 See also \fI--mail-rcpt\fP and \fI--mail-auth\fP. Added in 7.20.0.
1401 .IP "--mail-rcpt-allowfails"
1406 The default behavior can be changed by passing \fI--mail-rcpt-allowfails\fP
1407 command-line option which will make curl ignore errors and proceed with the
1413 .IP "--mail-rcpt <address>"
1414 (SMTP) Specify a single address, user name or mailing list name. Repeat this
1425 specified using the mailing list name, such as "Friends" or "London-Office".
1429 .IP "-M, --manual"
1431 .IP "--max-filesize <bytes>"
1444 See also \fI--limit-rate\fP.
1445 .IP "--max-redirs <num>"
1446 (HTTP) Set maximum number of redirection-followings allowed. When \fI-L, --location\fP is used,
1448 limit is set to 50 redirections. Set this option to -1 to make it unlimited.
1451 .IP "-m, --max-time <seconds>"
1460 See also \fI--connect-timeout\fP.
1461 .IP "--metalink"
1471  curl --metalink http://www.example.com/example.metalink
1475  curl --metalink file://example.metalink
1478 Metalink file at the time of this writing. Also note that if \fI--metalink\fP and
1479 \fI-i, --include\fP are used together, --include will be ignored. This is because
1484 \fI--metalink\fP requires that the underlying libcurl was built to support metalink. Added in 7.27.…
1485 .IP "--negotiate"
1488 This option requires a library built with GSS-API or SSPI support. Use
1489 \fI-V, --version\fP to see if your curl supports GSS-API/SSPI or SPNEGO.
1491 When using this option, you must also provide a fake \fI-u, --user\fP option to activate
1492 the authentication code properly. Sending a '-u :' is enough as the user name
1493 and password from the \fI-u, --user\fP option aren't actually used.
1497 See also \fI--basic\fP, \fI--ntlm\fP, \fI--anyauth\fP and \fI--proxy-negotiate\fP.
1498 .IP "--netrc-file <filename>"
1499 This option is similar to \fI-n, --netrc\fP, except that you provide the path (absolute
1501 netrc file per invocation. If several \fI--netrc-file\fP options are provided,
1504 It will abide by \fI--netrc-optional\fP if specified.
1506 This option overrides \fI-n, --netrc\fP. Added in 7.21.5.
1507 .IP "--netrc-optional"
1508 Very similar to \fI-n, --netrc\fP, but this option makes the .netrc usage \fBoptional\fP
1509 and not mandatory as the \fI-n, --netrc\fP option does.
1511 See also \fI--netrc-file\fP. This option overrides \fI-n, --netrc\fP.
1512 .IP "-n, --netrc"
1518 either world- or group-readable). The environment variable "HOME" is used to
1526 .IP "-:, --next"
1532 \fI-:, --next\fP will reset all local options and only global ones will have their
1533 values survive over to the operation following the \fI-:, --next\fP instruction. Global
1534 options include \fI-v, --verbose\fP, \fI--trace\fP, \fI--trace-ascii\fP and \fI--fail-early\fP.
1536 For example, you can do both a GET and a POST in a single command line:
1538  curl www1.example.com --next -d postthis www2.example.com
1541 .IP "--no-alpn"
1546 See also \fI--no-npn\fP and \fI--http2\fP. \fI--no-alpn\fP requires that the underlying libcurl was…
1547 .IP "-N, --no-buffer"
1554 --buffer to enforce the buffering.
1555 .IP "--no-keepalive"
1560 --keepalive to enforce keepalive.
1561 .IP "--no-npn"
1566 See also \fI--no-alpn\fP and \fI--http2\fP. \fI--no-npn\fP requires that the underlying libcurl was…
1567 .IP "--no-progress-meter"
1569 affecting warning and informational messages like \fI-s, --silent\fP does.
1572 --progress-meter to enable the progress meter again.
1574 See also \fI-v, --verbose\fP and \fI-s, --silent\fP. Added in 7.67.0.
1575 .IP "--no-sessionid"
1576 (TLS) Disable curl's use of SSL session-ID caching.  By default all transfers are
1578 attempting to reuse SSL session-IDs, there seem to be broken SSL
1583 --sessionid to enforce session-ID caching.
1586 .IP "--noproxy <no-proxy-list>"
1587 Comma-separated list of hosts which do not use a proxy, if one is specified.
1588 The only wildcard is a single * character, which matches all hosts, and
1599 .IP "--ntlm-wb"
1600 (HTTP) Enables NTLM much in the style \fI--ntlm\fP does, but hand over the authentication
1603 See also \fI--ntlm\fP and \fI--proxy-ntlm\fP.
1604 .IP "--ntlm"
1607 reverse-engineered by clever people and implemented in curl based on their
1613 \fI--proxy-ntlm\fP.
1617 …--proxy-ntlm\fP. \fI--ntlm\fP requires that the underlying libcurl was built to support TLS. This …
1618 .IP "--oauth2-bearer <token>"
1621 the \fI--url\fP or \fI-u, --user\fP options.
1626 .IP "--output-dir <dir>"
1629 \fI-O, --remote-name\fP or \fI-o, --output\fP are used.
1632 command line, up until the first \fI-:, --next\fP.
1634 If the specified target directory doesn't exist, the operation will fail
1635 unless \fI--create-dirs\fP is also used.
1640 See also \fI-O, --remote-name\fP and \fI-J, --remote-header-name\fP. Added in 7.73.0.
1641 .IP "-o, --output <file>"
1647  curl "http://{one,two}.example.com" -o "file_#1.txt"
1651  curl "http://{site,host}.host[1-5].com" -o "#1_#2"
1657   curl -o aa example.com -o bb example.net
1659 and the order of the -o options and the URLs doesn't matter, just that the
1660 first -o is for the first URL and so on, so the above command line can also be
1663   curl example.com example.net -o aa -o bb
1665 See also the \fI--create-dirs\fP option to create the local directories
1666 dynamically. Specifying the output as '-' (a single dash) will force the
1669 See also \fI-O, --remote-name\fP, \fI--remote-name-all\fP and \fI-J, --remote-header-name\fP.
1670 .IP "--parallel-immediate"
1676 See also \fI-Z, --parallel\fP and \fI--parallel-max\fP. Added in 7.68.0.
1677 .IP "--parallel-max"
1678 When asked to do parallel transfers, using \fI-Z, --parallel\fP, this option controls
1683 See also \fI-Z, --parallel\fP. Added in 7.66.0.
1684 .IP "-Z, --parallel"
1689 .IP "--pass <phrase>"
1693 .IP "--path-as-is"
1699 .IP "--pinnedpubkey <hashes>"
1701 peer. This can be a path to a file which contains a single public key in PEM
1720 .IP "--post301"
1722 requests when following a 301 redirection. The non-RFC behaviour is ubiquitous
1725 a redirection. This option is meaningful only when using \fI-L, --location\fP.
1727 See also \fI--post302\fP, \fI--post303\fP and \fI-L, --location\fP. Added in 7.17.1.
1728 .IP "--post302"
1730 requests when following a 302 redirection. The non-RFC behaviour is ubiquitous
1733 a redirection. This option is meaningful only when using \fI-L, --location\fP.
1735 See also \fI--post301\fP, \fI--post303\fP and \fI-L, --location\fP. Added in 7.19.1.
1736 .IP "--post303"
1740 using \fI-L, --location\fP.
1742 See also \fI--post302\fP, \fI--post301\fP and \fI-L, --location\fP. Added in 7.26.0.
1743 .IP "--preproxy [protocol://]host[:port]"
1744 Use the specified SOCKS proxy before connecting to an HTTP or HTTPS \fI-x, --proxy\fP. In
1763 .IP "-#, --progress-bar"
1767 This progress bar draws a single line of '#' characters across the screen and
1769 known size, there will be space ship (-=o=-) that moves back and forth but
1772 .IP "--proto-default <protocol>"
1777  curl --proto-default https ftp.mozilla.org
1784 Without this option curl would make a guess based on the host, see \fI--url\fP for
1788 .IP "--proto-redir <protocols>"
1790 \fI--proto\fP are not overridden by this option. See --proto for how protocols are
1795  curl --proto-redir -all,http,https http://example.com
1804 .IP "--proto <protocols>"
1814 .B -
1826 .B \fI--proto\fP -ftps
1829 .B  \fI--proto\fP -all,https,+http
1832 .B \fI--proto\fP =http,https
1843 See also \fI--proto-redir\fP and \fI--proto-default\fP. Added in 7.20.2.
1844 .IP "--proxy-anyauth"
1846 the given HTTP proxy. This might cause an extra request/response round-trip.
1848 See also \fI-x, --proxy\fP, \fI--proxy-basic\fP and \fI--proxy-digest\fP. Added in 7.13.2.
1849 .IP "--proxy-basic"
1851 proxy. Use \fI--basic\fP for enabling HTTP Basic with a remote host. Basic is the
1854 See also \fI-x, --proxy\fP, \fI--proxy-anyauth\fP and \fI--proxy-digest\fP.
1855 .IP "--proxy-cacert <file>"
1856 Same as \fI--cacert\fP but used in HTTPS proxy context.
1858 See also \fI--proxy-capath\fP, \fI--cacert\fP, \fI--capath\fP and \fI-x, --proxy\fP. Added in 7.52.…
1859 .IP "--proxy-capath <dir>"
1860 Same as \fI--capath\fP but used in HTTPS proxy context.
1862 See also \fI--proxy-cacert\fP, \fI-x, --proxy\fP and \fI--capath\fP. Added in 7.52.0.
1863 .IP "--proxy-cert-type <type>"
1864 Same as \fI--cert-type\fP but used in HTTPS proxy context.
1867 .IP "--proxy-cert <cert[:passwd]>"
1868 Same as \fI-E, --cert\fP but used in HTTPS proxy context.
1871 .IP "--proxy-ciphers <list>"
1872 Same as \fI--ciphers\fP but used in HTTPS proxy context.
1875 .IP "--proxy-crlfile <file>"
1876 Same as \fI--crlfile\fP but used in HTTPS proxy context.
1879 .IP "--proxy-digest"
1881 proxy. Use \fI--digest\fP for enabling HTTP Digest with a remote host.
1883 See also \fI-x, --proxy\fP, \fI--proxy-anyauth\fP and \fI--proxy-basic\fP.
1884 .IP "--proxy-header <header/@file>"
1886 specify any number of extra headers. This is the equivalent option to \fI-H, --header\fP
1891 end-of-line marker, you should thus \fBnot\fP add that as a part of the header
1899 then adds a header for each line in the input file. Using @- will make curl
1905 .IP "--proxy-insecure"
1906 Same as \fI-k, --insecure\fP but used in HTTPS proxy context.
1909 .IP "--proxy-key-type <type>"
1910 Same as \fI--key-type\fP but used in HTTPS proxy context.
1913 .IP "--proxy-key <key>"
1914 Same as \fI--key\fP but used in HTTPS proxy context.
1915 .IP "--proxy-negotiate"
1917 with the given proxy. Use \fI--negotiate\fP for enabling HTTP Negotiate (SPNEGO)
1920 See also \fI--proxy-anyauth\fP and \fI--proxy-basic\fP. Added in 7.17.1.
1921 .IP "--proxy-ntlm"
1923 proxy. Use \fI--ntlm\fP for enabling NTLM with a remote host.
1925 See also \fI--proxy-negotiate\fP and \fI--proxy-anyauth\fP.
1926 .IP "--proxy-pass <phrase>"
1927 Same as \fI--pass\fP but used in HTTPS proxy context.
1930 .IP "--proxy-pinnedpubkey <hashes>"
1932 proxy. This can be a path to a file which contains a single public key in PEM
1942 .IP "--proxy-service-name <name>"
1946 .IP "--proxy-ssl-allow-beast"
1947 Same as \fI--ssl-allow-beast\fP but used in HTTPS proxy context.
1950 .IP "--proxy-tls13-ciphers <ciphersuite list>"
1955  https://curl.haxx.se/docs/ssl-ciphers.html
1959 cipher suites by using the \fI--proxy-ciphers\fP option.
1962 .IP "--proxy-tlsauthtype <type>"
1963 Same as \fI--tlsauthtype\fP but used in HTTPS proxy context.
1966 .IP "--proxy-tlspassword <string>"
1967 Same as \fI--tlspassword\fP but used in HTTPS proxy context.
1970 .IP "--proxy-tlsuser <name>"
1971 Same as \fI--tlsuser\fP but used in HTTPS proxy context.
1974 .IP "--proxy-tlsv1"
1975 Same as \fI-1, --tlsv1\fP but used in HTTPS proxy context.
1978 .IP "-U, --proxy-user <user:password>"
1981 If you use a Windows SSPI-enabled curl binary and do either Negotiate or NTLM
1983 from your environment by specifying a single colon with this option: "-U :".
1992 .IP "-x, --proxy [protocol://]host[:port]"
2016 one with the \fI-p, --proxytunnel\fP option.
2027 .IP "--proxy1.0 <host[:port]>"
2031 The only difference between this and the HTTP proxy option \fI-x, --proxy\fP, is that
2034 .IP "-p, --proxytunnel"
2035 When an HTTP proxy is used \fI-x, --proxy\fP, this option will make curl tunnel through
2041 use \fI--suppress-connect-headers\fP.
2043 See also \fI-x, --proxy\fP.
2044 .IP "--pubkey <key>"
2054 .IP "-Q, --quote"
2059 transfer, prefix them with a dash '-'.  To make commands be sent after curl
2075 shell-style to embed spaces or special characters.  Following is the list of
2104 .IP "rename source target"
2106 operand to the destination path named by the target operand.
2115 .IP "--random-file <file>"
2118 also the \fI--egd-file\fP option.
2119 .IP "-r, --range <range>"
2124 .B 0-499
2127 .B 500-999
2130 .B -500
2133 .B 9500-
2136 .B 0-0,-1
2139 .B 100-199,500-599
2140 specifies two separate 100-byte ranges(*) (HTTP)
2146 Only digit characters (0-9) are valid in the 'start' and 'stop' fields of the
2147 \&'start-stop' range syntax. If a non-digit character is given in the range,
2155 FTP and SFTP range downloads only support the simple 'start-stop' syntax
2160 .IP "--raw"
2165 .IP "-e, --referer <URL>"
2167 with the \fI-H, --header\fP flag of course.  When used with \fI-L, --location\fP you can append
2168 ";auto" to the \fI-e, --referer\fP URL to make curl automatically set the previous URL
2170 even if you don't set an initial \fI-e, --referer\fP.
2174 See also \fI-A, --user-agent\fP and \fI-H, --header\fP.
2175 .IP "-J, --remote-header-name"
2176 (HTTP) This option tells the \fI-O, --remote-name\fP option to use the server-specified
2177 Content-Disposition filename instead of extracting a filename from the URL.
2184 There's no attempt to decode %-sequences (yet) in the provided file name, so
2190 .IP "--remote-name-all"
2192 if \fI-O, --remote-name\fP were used for each one. So if you want to disable that for a
2193 specific URL after \fI--remote-name-all\fP has been used, you must use "-o -" or
2194 --no-remote-name.
2197 .IP "-O, --remote-name"
2207 server to be able to choose the file name refer to \fI-J, --remote-header-name\fP which
2212 encoded parts of the name, they will end up as-is as file name.
2215 .IP "-R, --remote-time"
2219 .IP "--request-target"
2220 (HTTP) Tells curl to use an alternative "target" (path) instead of using the path as
2226 .IP "-X, --request <command>"
2239 request, using -X HEAD will not suffice. You need to use the \fI-I, --head\fP option.
2241 The method string you set with \fI-X, --request\fP will be used for all requests, which
2242 if you for example use \fI-L, --location\fP may cause unintended side-effects when curl
2243 doesn't change request method according to the HTTP 30x response codes - and
2261 .IP "--resolve <host:port:addr[,addr]...>"
2271 port pair to the specified address. Wildcard is resolved last so any \fI--resolve\fP
2274 The provided address set by this option will be used even if \fI-4, --ipv4\fP or \fI-6, --ipv6\fP
2286 .IP "--retry-all-errors"
2287 Retry on any error. This option is used together with \fI--retry\fP.
2304 .IP "--retry-connrefused"
2306 error too for \fI--retry\fP. This option is used together with --retry.
2309 .IP "--retry-delay <seconds>"
2312 between retries). This option is only interesting if \fI--retry\fP is also
2318 .IP "--retry-max-time <seconds>"
2320 done as usual (see \fI--retry\fP) as long as the timer hasn't reached this given
2323 limit a single request\'s maximum time, use \fI-m, --max-time\fP.  Set this option to
2329 .IP "--retry <num>"
2338 using \fI--retry-delay\fP you disable this exponential backoff algorithm. See also
2339 \fI--retry-max-time\fP to limit the total time allowed for retries.
2341 Since curl 7.66.0, curl will comply with the Retry-After: response header if
2347 .IP "--sasl-authzid <identity>"
2349 in addition to the authentication identity (authcid) as specified by \fI-u, --user\fP.
2357 .IP "--sasl-ir"
2361 .IP "--service-name <name>"
2364 Examples: \fI--negotiate\fP \fI--service-name\fP sockd would use sockd/server-name.
2367 .IP "-S, --show-error"
2368 When used with \fI-s, --silent\fP, it makes curl show an error message if it fails.
2370 See also \fI--no-progress-meter\fP.
2371 .IP "-s, --silent"
2376 Use \fI-S, --show-error\fP in addition to this option to disable progress meter but
2379 See also \fI-v, --verbose\fP, \fI--stderr\fP and \fI--no-progress-meter\fP.
2380 .IP "--socks4 <host[:port]>"
2384 This option overrides any previous use of \fI-x, --proxy\fP, as they are mutually
2388 with \fI-x, --proxy\fP using a socks4:// protocol prefix.
2390 Since 7.52.0, \fI--preproxy\fP can be used to specify a SOCKS proxy at the same time
2391 \fI-x, --proxy\fP is used with an HTTP/HTTPS proxy. In such a case curl first connects to
2397 .IP "--socks4a <host[:port]>"
2401 This option overrides any previous use of \fI-x, --proxy\fP, as they are mutually
2405 with \fI-x, --proxy\fP using a socks4a:// protocol prefix.
2407 Since 7.52.0, \fI--preproxy\fP can be used to specify a SOCKS proxy at the same time
2408 \fI-x, --proxy\fP is used with an HTTP/HTTPS proxy. In such a case curl first connects to
2414 .IP "--socks5-basic"
2417 \fI--socks5-gssapi\fP to force GSS-API authentication to SOCKS5 proxies.
2420 .IP "--socks5-gssapi-nec"
2421 As part of the GSS-API negotiation a protection mode is negotiated. RFC 1961
2423 implementation does not.  The option \fI--socks5-gssapi-nec\fP allows the
2427 .IP "--socks5-gssapi-service <name>"
2428 The default service name for a socks server is rcmd/server-fqdn. This option
2431 Examples: \fI--socks5\fP proxy-name \fI--socks5-gssapi-service\fP sockd would use
2432 sockd/proxy-name \fI--socks5\fP proxy-name \fI--socks5-gssapi-service\fP sockd/real-name
2433 would use sockd/real-name for cases where the proxy-name does not match the
2437 .IP "--socks5-gssapi"
2438 Tells curl to use GSS-API authentication when connecting to a SOCKS5 proxy.
2439 The GSS-API authentication is enabled by default (if curl is compiled with
2440 GSS-API support).  Use \fI--socks5-basic\fP to force username/password authentication
2444 .IP "--socks5-hostname <host[:port]>"
2448 This option overrides any previous use of \fI-x, --proxy\fP, as they are mutually
2452 hostname proxy with \fI-x, --proxy\fP using a socks5h:// protocol prefix.
2454 Since 7.52.0, \fI--preproxy\fP can be used to specify a SOCKS proxy at the same time
2455 \fI-x, --proxy\fP is used with an HTTP/HTTPS proxy. In such a case curl first connects to
2461 .IP "--socks5 <host[:port]>"
2462 Use the specified SOCKS5 proxy - but resolve the host name locally. If the
2465 This option overrides any previous use of \fI-x, --proxy\fP, as they are mutually
2469 with \fI-x, --proxy\fP using a socks5:// protocol prefix.
2471 Since 7.52.0, \fI--preproxy\fP can be used to specify a SOCKS proxy at the same time
2472 \fI-x, --proxy\fP is used with an HTTP/HTTPS proxy. In such a case curl first connects to
2477 This option (as well as \fI--socks4\fP) does not work with IPV6, FTPS or LDAP.
2480 .IP "-Y, --speed-limit <speed>"
2482 speed-time seconds it gets aborted. speed-time is set with \fI-y, --speed-time\fP and is
2486 .IP "-y, --speed-time <seconds>"
2487 If a download is slower than speed-limit bytes per second during a speed-time
2488 period, the download gets aborted. If speed-time is used, the default
2489 speed-limit will be 1 unless set with \fI-Y, --speed-limit\fP.
2492 this is a concern for you, try the \fI--connect-timeout\fP option.
2495 .IP "--ssl-allow-beast"
2503 .IP "--ssl-no-revoke"
2509 .IP "--ssl-reqd"
2513 This option was formerly known as --ftp-ssl-reqd.
2516 .IP "--ssl-revoke-best-effort"
2522 .IP "--ssl"
2524 Try to use SSL/TLS for the connection.  Reverts to a non-secure connection if
2525 the server doesn't support SSL/TLS.  See also \fI--ftp-ssl-control\fP and \fI--ssl-reqd\fP
2528 This option was formerly known as --ftp-ssl (Added in 7.11.0). That option
2532 .IP "-2, --sslv2"
2537 …--http1.1\fP and \fI--http2\fP. \fI-2, --sslv2\fP requires that the underlying libcurl was built t…
2538 .IP "-3, --sslv3"
2543 …--http1.1\fP and \fI--http2\fP. \fI-3, --sslv3\fP requires that the underlying libcurl was built t…
2544 .IP "--stderr"
2546 is a plain '-', it is instead written to stdout.
2550 See also \fI-v, --verbose\fP and \fI-s, --silent\fP.
2551 .IP "--styled-output"
2553 terminal. Use --no-styled-output to switch them off.
2556 .IP "--suppress-connect-headers"
2557 When \fI-p, --proxytunnel\fP is used and a CONNECT request is made don't output proxy
2558 CONNECT response headers. This option is meant to be used with \fI-D, --dump-header\fP or
2559 \fI-i, --include\fP which are used to show protocol headers in the output. It has no
2560 effect on debug options such as \fI-v, --verbose\fP or \fI--trace\fP, or any statistics.
2562 See also \fI-D, --dump-header\fP, \fI-i, --include\fP and \fI-p, --proxytunnel\fP.
2563 .IP "--tcp-fastopen"
2567 .IP "--tcp-nodelay"
2575 .IP "-t, --telnet-option <opt=val>"
2583 .IP "--tftp-blksize <value>"
2591 .IP "--tftp-no-options"
2595 or properly implement TFTP options. When this option is used \fI--tftp-blksize\fP is
2599 .IP "-z, --time-cond <time>"
2606 Start the date expression with a dash (-) to make it request for a document
2611 .IP "--tls-max <VERSION>"
2616 includes QUIC-using (HTTP/3) transfers.
2631 See also \fI--tlsv1.0\fP, \fI--tlsv1.1\fP, \fI--tlsv1.2\fP and \fI--tlsv1.3\fP. \fI--tls-max\fP req…
2632 .IP "--tls13-ciphers <ciphersuite list>"
2637  https://curl.haxx.se/docs/ssl-ciphers.html
2641 cipher suites by using the \fI--ciphers\fP option.
2644 .IP "--tlsauthtype <type>"
2646 for TLS-SRP (RFC 5054). If \fI--tlsuser\fP and \fI--tlspassword\fP are specified but
2647 \fI--tlsauthtype\fP is not, then this option defaults to "SRP".  This option works
2648 only if the underlying libcurl is built with TLS-SRP support, which requires
2649 OpenSSL or GnuTLS with TLS-SRP support.
2652 .IP "--tlspassword"
2654 \fI--tlsauthtype\fP. Requires that \fI--tlsuser\fP also be set.
2659 .IP "--tlsuser <name>"
2661 \fI--tlsauthtype\fP. Requires that \fI--tlspassword\fP also is set.
2666 .IP "--tlsv1.0"
2670 but behavior was inconsistent depending on the TLS library. Use \fI--tls-max\fP if
2674 .IP "--tlsv1.1"
2678 but behavior was inconsistent depending on the TLS library. Use \fI--tls-max\fP if
2682 .IP "--tlsv1.2"
2686 but behavior was inconsistent depending on the TLS library. Use \fI--tls-max\fP if
2690 .IP "--tlsv1.3"
2695 includes QUIC-using (HTTP/3) transfers.
2700 .IP "-1, --tlsv1"
2704 …--http1.1\fP and \fI--http2\fP. \fI-1, --tlsv1\fP requires that the underlying libcurl was built t…
2705 .IP "--tr-encoding"
2706 (HTTP) Request a compressed Transfer-Encoding response using one of the algorithms
2710 .IP "--trace-ascii <file>"
2712 descriptive information, to the given output file. Use "-" as filename to have
2715 This is very similar to \fI--trace\fP, but leaves out the hex part and only shows
2721 This option overrides \fI--trace\fP and \fI-v, --verbose\fP.
2722 .IP "--trace-time"
2726 .IP "--trace <file>"
2728 descriptive information, to the given output file. Use "-" as filename to have
2734 This option overrides \fI-v, --verbose\fP and \fI--trace-ascii\fP.
2735 .IP "--unix-socket <path>"
2739 .IP "-T, --upload-file <file>"
2747 Use the file name "-" (a single dash) to use stdin instead of a given file.
2748 Alternately, the file name "." (a single period) may be specified instead
2749 of "-" to use stdin in non-blocking mode to allow reading server output
2752 You can specify one \fI-T, --upload-file\fP for each URL on the command line. Each
2753 \fI-T, --upload-file\fP + URL pair specifies what to upload and to where. curl also
2754 supports "globbing" of the \fI-T, --upload-file\fP argument, meaning that you can upload
2755 multiple files to a single URL by using the same URL globbing style supported
2758  curl --upload-file "{file1,file2}" http://www.example.com
2762  curl -T "img[1-1000].png" ftp://ftp.example.com/upload/
2768 .IP "--url <url>"
2773 then curl will make a guess based on the host. If the outermost sub-domain
2776 setting a default protocol, see \fI--proto-default\fP for details.
2779 written, use the \fI-o, --output\fP or the \fI-O, --remote-name\fP options.
2783 .IP "-B, --use-ascii"
2787 .IP "-A, --user-agent <name>"
2789 Specify the User-Agent string to send to the HTTP server. To encode blanks in
2790 the string, surround the string with single quote marks. This header can also
2791 be set with the \fI-H, --header\fP or the \fI--proxy-header\fP options.
2793 If you give an empty argument to \fI-A, --user-agent\fP (""), it will remove the header
2795 single space (" ").
2798 .IP "-u, --user <user:password>"
2800 \fI-n, --netrc\fP and \fI--netrc-optional\fP.
2820 without the domain, if there is a single domain and forest in your setup
2823 To specify the domain name use either Down-Level Logon Name or UPN (User
2827 If you use a Windows SSPI-enabled curl binary and perform Kerberos V5,
2829 the user name and password from your environment by specifying a single colon
2830 with this option: "-u :".
2833 .IP "-v, --verbose"
2840 If you only want HTTP headers in the output, \fI-i, --include\fP might be the option
2844 \fI--trace\fP or \fI--trace-ascii\fP instead.
2846 Use \fI-s, --silent\fP to make curl really quiet.
2848 See also \fI-i, --include\fP. This option overrides \fI--trace\fP and \fI--trace-ascii\fP.
2849 .IP "-V, --version"
2861 .IP "alt-svc"
2862 Support for the Alt-Svc: header is provided.
2865 done using either the c-ares or the threaded resolver backends.
2871 This curl uses a libcurl built with Debug. This enables more error-tracking
2872 and memory debugging etc. For curl-developers only!
2873 .IP "GSS-API"
2874 GSS-API is supported.
2876 HTTP/2 support has been built-in.
2878 HTTP/3 support has been built-in.
2879 .IP "HTTPS-proxy"
2882 This curl supports IDN - international domain names.
2909 .IP "TLS-SRP"
2914 .IP "-w, --write-out <format>"
2919 format from stdin you write "@-".
2931 The %-symbol is a special symbol in the win32-environment, where all
2938 The Content-Type of the requested document, if there was any.
2942 is told to write to a file with the \fI-O, --remote-name\fP or \fI-o, --output\fP
2943 option. It's most useful in combination with the \fI-J, --remote-header-name\fP
2966 The IP address of the local end of the most recently done connection - can be
2967 either IPv4 or IPv6 (Added in 7.29.0)
2990 When an HTTP request was made without \fI-L, --location\fP to follow redirects (or when
2991 --max-redir is met), this variable will show the actual URL a redirect
2995 The remote IP address of the most recently done connection - can be either
2996 IPv4 or IPv6 (Added in 7.29.0)
3033 From this point on, the \fI-w, --write-out\fP output will be written to standard
3037 From this point on, the \fI-w, --write-out\fP output will be written to standard output.
3055 about to begin. This includes all pre-transfer commands and negotiations that
3078 .IP "--xattr"
3087 Default config file, see \fI-K, --config\fP for details.
3094 the \fI-x, --proxy\fP option.
3100 .IP "[url-protocol]_PROXY [protocol://]<host>[:port]"
3101 Sets the proxy server to use for [url-protocol], where the protocol is a
3105 Sets the proxy server to use if no protocol-specific proxy is set.
3106 .IP "NO_PROXY <comma-separated list of hosts/domains>"
3112 the \fI-x, --proxy\fP option. That is
3113 .B NO_PROXY=direct.example.com curl -x http://proxy.example.com
3115 accesses the target URL directly, and
3116 .B NO_PROXY=direct.example.com curl -x http://proxy.example.com
3118 accesses the target URL through the proxy.
3127 If curl was built with support for "MultiSSL", meaning that it has built-in
3130 invoked. Setting a name that isn't a built-in alternative, will make curl
3156 Makes it the equivalent of \fI--socks4\fP
3158 Makes it the equivalent of \fI--socks4a\fP
3160 Makes it the equivalent of \fI--socks5\fP
3162 Makes it the equivalent of \fI--socks5-hostname\fP
3175 enabled or was explicitly disabled at build-time. To make curl able to do
3201 FTP weird 227 format. Curl couldn't parse the 227-line the server sent.
3203 FTP can't get host. Couldn't resolve the host IP we got in the 227-line.
3220 appears if \fI-f, --fail\fP is used.
3231 Operation timeout. The specified time-out period was reached according to the
3242 HTTP post error. Internal post-request generation error.