commit 745e02c
hovercats
·
2024-02-02 11:39:27 +0000 UTC
parent 00fd516
curl: bump to 8.6.0 Upstream has decided that curl.1 should be generated instead of included as a standalone file.
8 files changed,
+6095,
-16
+1,
-1
1@@ -1,2 +1,2 @@
2-/curl-8.5.0.tar.gz
3+/curl-8.6.0.tar.gz
4 /src
+1,
-0
1@@ -8,6 +8,7 @@ Generated with
2 --disable-smb \
3 --with-ca-bundle=/etc/ssl/cert.pem \
4 --with-bearssl \
5+ --without-libpsl \
6 CPPFLAGS='-I/src/oasis/out/pkg/bearssl/include -I/src/oasis/out/pkg/zlib/include' \
7 LDFLAGS='-L/src/oasis/out/pkg/bearssl -L/src/oasis/out/pkg/zlib'
8
+6076,
-0
1@@ -0,0 +1,6076 @@
2+.\" **************************************************************************
3+.\" * _ _ ____ _
4+.\" * Project ___| | | | _ \| |
5+.\" * / __| | | | |_) | |
6+.\" * | (__| |_| | _ <| |___
7+.\" * \___|\___/|_| \_\_____|
8+.\" *
9+.\" * Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
10+.\" *
11+.\" * This software is licensed as described in the file COPYING, which
12+.\" * you should have received as part of this distribution. The terms
13+.\" * are also available at https://curl.se/docs/copyright.html.
14+.\" *
15+.\" * You may opt to use, copy, modify, merge, publish, distribute and/or sell
16+.\" * copies of the Software, and permit persons to whom the Software is
17+.\" * furnished to do so, under the terms of the COPYING file.
18+.\" *
19+.\" * This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
20+.\" * KIND, either express or implied.
21+.\" *
22+.\" * SPDX-License-Identifier: curl
23+.\" *
24+.\" **************************************************************************
25+.\"
26+.\" DO NOT EDIT. Generated by the curl project gen.pl man page generator.
27+.\"
28+.TH curl 1 "February 02 2024" "curl 8.6.0" "curl Manual"
29+.SH NAME
30+curl \- transfer a URL
31+.SH SYNOPSIS
32+\fBcurl [options / URLs]\fP
33+.SH DESCRIPTION
34+\fBcurl\fP is a tool for transferring data from or to a server using URLs. It
35+supports these protocols: DICT, FILE, FTP, FTPS, GOPHER, GOPHERS, HTTP, HTTPS,
36+IMAP, IMAPS, LDAP, LDAPS, MQTT, POP3, POP3S, RTMP, RTMPS, RTSP, SCP, SFTP,
37+SMB, SMBS, SMTP, SMTPS, TELNET, TFTP, WS and WSS.
38+
39+curl is powered by libcurl for all transfer\-related features. See
40+\fIlibcurl(3)\fP for details.
41+.SH URL
42+The URL syntax is protocol\-dependent. You find a detailed description in
43+RFC 3986.
44+
45+If you provide a URL without a leading \fBprotocol://\fP scheme, curl guesses
46+what protocol you want. It then defaults to HTTP but assumes others based on
47+often\-used host name prefixes. For example, for host names starting with
48+\&"ftp." curl assumes you want FTP.
49+
50+You can specify any amount of URLs on the command line. They are fetched in a
51+sequential manner in the specified order unless you use \fI\-Z, \-\-parallel\fP. You can
52+specify command line options and URLs mixed and in any order on the command
53+line.
54+
55+curl attempts to reuse connections when doing multiple transfers, so that
56+getting many files from the same server do not use multiple connects and setup
57+handshakes. This improves speed. Connection reuse can only be done for URLs
58+specified for a single command line invocation and cannot be performed between
59+separate curl runs.
60+
61+Provide an IPv6 zone id in the URL with an escaped percentage sign. Like in
62+.nf
63+
64+\&"http://[fe80::3%25eth0]/"
65+.fi
66+
67+Everything provided on the command line that is not a command line option or
68+its argument, curl assumes is a URL and treats it as such.
69+.SH GLOBBING
70+You can specify multiple URLs or parts of URLs by writing lists within braces
71+or ranges within brackets. We call this "globbing".
72+
73+Provide a list with three different names like this:
74+.nf
75+
76+\&"http://site.{one,two,three}.com"
77+.fi
78+
79+Do sequences of alphanumeric series by using [] as in:
80+.nf
81+
82+\&"ftp://ftp.example.com/file[1\-100].txt"
83+.fi
84+
85+With leading zeroes:
86+.nf
87+
88+\&"ftp://ftp.example.com/file[001\-100].txt"
89+.fi
90+
91+With letters through the alphabet:
92+.nf
93+
94+\&"ftp://ftp.example.com/file[a\-z].txt"
95+.fi
96+
97+Nested sequences are not supported, but you can use several ones next to each
98+other:
99+.nf
100+
101+\&"http://example.com/archive[1996\-1999]/vol[1\-4]/part{a,b,c}.html"
102+.fi
103+
104+You can specify a step counter for the ranges to get every Nth number or
105+letter:
106+.nf
107+
108+\&"http://example.com/file[1\-100:10].txt"
109+
110+\&"http://example.com/file[a\-z:2].txt"
111+.fi
112+
113+When using [] or {} sequences when invoked from a command line prompt, you
114+probably have to put the full URL within double quotes to avoid the shell from
115+interfering with it. This also goes for other characters treated special, like
116+for example \(aq&\(aq, \(aq?\(aq and \(aq*\(aq.
117+
118+Switch off globbing with \fI\-g, \-\-globoff\fP.
119+.SH VARIABLES
120+curl supports command line variables (added in 8.3.0). Set variables with
121+\fI\-\-variable\fP name=content or \fI\-\-variable\fP name@file (where "file" can be stdin if
122+set to a single dash (\-)).
123+
124+Variable contents can be expanded in option parameters using "{{name}}" (without
125+the quotes) if the option name is prefixed with "\--expand\-". This gets the
126+contents of the variable "name" inserted, or a blank if the name does not
127+exist as a variable. Insert "{{" verbatim in the string by prefixing it with a
128+backslash, like "\\{{".
129+
130+You an access and expand environment variables by first importing them. You
131+can select to either require the environment variable to be set or you can
132+provide a default value in case it is not already set. Plain \fI\-\-variable\fP %name
133+imports the variable called \(aqname\(aq but exits with an error if that environment
134+variable is not already set. To provide a default value if it is not set, use
135+\fI\-\-variable\fP %name=content or \fI\-\-variable\fP %name@content.
136+
137+Example. Get the USER environment variable into the URL, fail if USER is not
138+set:
139+.nf
140+
141+-\-variable \(aq%USER\(aq
142+-\-expand\-url = "https://example.com/api/{{USER}}/method"
143+.fi
144+
145+When expanding variables, curl supports a set of functions that can make the
146+variable contents more convenient to use. It can trim leading and trailing
147+white space with \fItrim\fP, it can output the contents as a JSON quoted string
148+with \fIjson\fP, URL encode the string with \fIurl\fP or base64 encode it with
149+\fIb64\fP. You apply function to a variable expansion, add them colon separated to
150+the right side of the variable. Variable content holding null bytes that are
151+not encoded when expanded cause error.
152+
153+Example: get the contents of a file called $HOME/.secret into a variable
154+called "fix". Make sure that the content is trimmed and percent\-encoded sent
155+as POST data:
156+.nf
157+
158+-\-variable %HOME
159+-\-expand\-variable fix@{{HOME}}/.secret
160+-\-expand\-data "{{fix:trim:url}}"
161+https://example.com/
162+.fi
163+
164+Command line variables and expansions were added in in 8.3.0.
165+.SH OUTPUT
166+If not told otherwise, curl writes the received data to stdout. It can be
167+instructed to instead save that data into a local file, using the \fI\-o, \-\-output\fP or
168+\fI\-O, \-\-remote\-name\fP options. If curl is given multiple URLs to transfer on the
169+command line, it similarly needs multiple options for where to save them.
170+
171+curl does not parse or otherwise "understand" the content it gets or writes as
172+output. It does no encoding or decoding, unless explicitly asked to with
173+dedicated command line options.
174+.SH PROTOCOLS
175+curl supports numerous protocols, or put in URL terms: schemes. Your
176+particular build may not support them all.
177+.IP DICT
178+Lets you lookup words using online dictionaries.
179+.IP FILE
180+Read or write local files. curl does not support accessing file:// URL
181+remotely, but when running on Microsoft Windows using the native UNC approach
182+works.
183+.IP FTP(S)
184+curl supports the File Transfer Protocol with a lot of tweaks and levers. With
185+or without using TLS.
186+.IP GOPHER(S)
187+Retrieve files.
188+.IP HTTP(S)
189+curl supports HTTP with numerous options and variations. It can speak HTTP
190+version 0.9, 1.0, 1.1, 2 and 3 depending on build options and the correct
191+command line options.
192+.IP IMAP(S)
193+Using the mail reading protocol, curl can "download" emails for you. With or
194+without using TLS.
195+.IP LDAP(S)
196+curl can do directory lookups for you, with or without TLS.
197+.IP MQTT
198+curl supports MQTT version 3. Downloading over MQTT equals "subscribe" to a
199+topic while uploading/posting equals "publish" on a topic. MQTT over TLS is
200+not supported (yet).
201+.IP POP3(S)
202+Downloading from a pop3 server means getting a mail. With or without using
203+TLS.
204+.IP RTMP(S)
205+The \fBRealtime Messaging Protocol\fP is primarily used to serve streaming media
206+and curl can download it.
207+.IP RTSP
208+curl supports RTSP 1.0 downloads.
209+.IP SCP
210+curl supports SSH version 2 scp transfers.
211+.IP SFTP
212+curl supports SFTP (draft 5) done over SSH version 2.
213+.IP SMB(S)
214+curl supports SMB version 1 for upload and download.
215+.IP SMTP(S)
216+Uploading contents to an SMTP server means sending an email. With or without
217+TLS.
218+.IP TELNET
219+Telling curl to fetch a telnet URL starts an interactive session where it
220+sends what it reads on stdin and outputs what the server sends it.
221+.IP TFTP
222+curl can do TFTP downloads and uploads.
223+.SH "PROGRESS METER"
224+curl normally displays a progress meter during operations, indicating the
225+amount of transferred data, transfer speeds and estimated time left, etc. The
226+progress meter displays the transfer rate in bytes per second. The suffixes
227+(k, M, G, T, P) are 1024 based. For example 1k is 1024 bytes. 1M is 1048576
228+bytes.
229+
230+curl displays this data to the terminal by default, so if you invoke curl to
231+do an operation and it is about to write data to the terminal, it \fIdisables\fP
232+the progress meter as otherwise it would mess up the output mixing progress
233+meter and response data.
234+
235+If you want a progress meter for HTTP POST or PUT requests, you need to
236+redirect the response output to a file, using shell redirect (>), \fI\-o, \-\-output\fP or
237+similar.
238+
239+This does not apply to FTP upload as that operation does not spit out any
240+response data to the terminal.
241+
242+If you prefer a progress "bar" instead of the regular meter, \fI\-#, \-\-progress\-bar\fP is
243+your friend. You can also disable the progress meter completely with the
244+\fI\-s, \-\-silent\fP option.
245+.SH VERSION
246+This man page describes curl %VERSION. If you use a later version, chances are
247+this man page does not fully document it. If you use an earlier version, this
248+document tries to include version information about which specific version
249+that introduced changes.
250+
251+You can always learn which the latest curl version is by running
252+.nf
253+
254+curl https://curl.se/info
255+.fi
256+
257+The online version of this man page is always showing the latest incarnation:
258+https://curl.se/docs/manpage.html
259+.SH OPTIONS
260+Options start with one or two dashes. Many of the options require an
261+additional value next to them. If provided text does not start with a dash, it
262+is presumed to be and treated as a URL.
263+
264+The short "single\-dash" form of the options, \-d for example, may be used with
265+or without a space between it and its value, although a space is a recommended
266+separator. The long "double\-dash" form, \fI\-d, \-\-data\fP for example, requires a space
267+between it and its value.
268+
269+Short version options that do not need any additional values can be used
270+immediately next to each other, like for example you can specify all the
271+options \fI\-O\fP, \fI\-L\fP and \fI\-v\fP at once as \fI\-OLv\fP.
272+
273+In general, all boolean options are enabled with \--\fBoption\fP and yet again
274+disabled with \--\fBno\-\fPoption. That is, you use the same option name but
275+prefix it with "no\-". However, in this list we mostly only list and show the
276+\fI\--option\fP version of them.
277+
278+When \fI\-:, \-\-next\fP is used, it resets the parser state and you start again with a
279+clean option state, except for the options that are "global". Global options
280+retain their values and meaning even after \fI\-:, \-\-next\fP.
281+
282+The following options are global: \fI\-\-fail\-early\fP, \fI\-\-libcurl\fP, \fI\-\-parallel\-immediate\fP, \fI\-Z, \-\-parallel\fP, \fI\-#, \-\-progress\-bar\fP, \fI\-\-rate\fP, \fI\-S, \-\-show\-error\fP, \fI\-\-stderr\fP, \fI\-\-styled\-output\fP, \fI\-\-trace\-ascii\fP, \fI\-\-trace\-config\fP, \fI\-\-trace\-ids\fP, \fI\-\-trace\-time\fP, \fI\-\-trace\fP and \fI\-v, \-\-verbose\fP.
283+.IP "\-\-abstract\-unix\-socket <path>"
284+(HTTP) Connect through an abstract Unix domain socket, instead of using the network.
285+Note: netstat shows the path of an abstract socket prefixed with \(aq@\(aq, however
286+the <path> argument should not have this leading character.
287+
288+If --abstract-unix-socket is provided several times, the last set value is used.
289+
290+Example:
291+.nf
292+ curl --abstract-unix-socket socketpath https://example.com
293+.fi
294+
295+See also \fI\-\-unix\-socket\fP. Added in 7.53.0.
296+.IP "\-\-alt\-svc <file name>"
297+(HTTPS) This option enables the alt\-svc parser in curl. If the file name points to an
298+existing alt\-svc cache file, that gets used. After a completed transfer, the
299+cache is saved to the file name again if it has been modified.
300+
301+Specify a "" file name (zero length) to avoid loading/saving and make curl
302+just handle the cache in memory.
303+
304+If this option is used several times, curl loads contents from all the
305+files but the last one is used for saving.
306+
307+--alt-svc can be used several times in a command line
308+
309+Example:
310+.nf
311+ curl --alt-svc svc.txt https://example.com
312+.fi
313+
314+See also \fI\-\-resolve\fP and \fI\-\-connect\-to\fP. Added in 7.64.1.
315+.IP "\-\-anyauth"
316+(HTTP) Tells curl to figure out authentication method by itself, and use the most
317+secure one the remote site claims to support. This is done by first doing a
318+request and checking the response\-headers, thus possibly inducing an extra
319+network round\-trip. This is used instead of setting a specific authentication
320+method, which you can do with \fI\-\-basic\fP, \fI\-\-digest\fP, \fI\-\-ntlm\fP, and \fI\-\-negotiate\fP.
321+
322+Using \fI\-\-anyauth\fP is not recommended if you do uploads from stdin, since it may
323+require data to be sent twice and then the client must be able to rewind. If
324+the need should arise when uploading from stdin, the upload operation fails.
325+
326+Used together with \fI\-u, \-\-user\fP.
327+
328+Providing --anyauth multiple times has no extra effect.
329+
330+Example:
331+.nf
332+ curl --anyauth --user me:pwd https://example.com
333+.fi
334+
335+See also \fI\-\-proxy\-anyauth\fP, \fI\-\-basic\fP and \fI\-\-digest\fP.
336+.IP "\-a, \-\-append"
337+(FTP SFTP) When used in an upload, this option makes curl append to the target file
338+instead of overwriting it. If the remote file does not exist, it is
339+created. Note that this flag is ignored by some SFTP servers (including
340+OpenSSH).
341+
342+Providing --append multiple times has no extra effect.
343+Disable it again with \-\-no-append.
344+
345+Example:
346+.nf
347+ curl --upload-file local --append ftp://example.com/
348+.fi
349+
350+See also \fI-r, \-\-range\fP and \fI-C, \-\-continue\-at\fP.
351+.IP "\-\-aws\-sigv4 <provider1[:provider2[:region[:service]]]>"
352+(HTTP) Use AWS V4 signature authentication in the transfer.
353+
354+The provider argument is a string that is used by the algorithm when creating
355+outgoing authentication headers.
356+
357+The region argument is a string that points to a geographic area of
358+a resources collection (region\-code) when the region name is omitted from
359+the endpoint.
360+
361+The service argument is a string that points to a function provided by a cloud
362+(service\-code) when the service name is omitted from the endpoint.
363+
364+If --aws-sigv4 is provided several times, the last set value is used.
365+
366+Example:
367+.nf
368+ curl --aws-sigv4 "aws:amz:us-east-2:es" --user "key:secret" https://example.com
369+.fi
370+
371+See also \fI\-\-basic\fP and \fI-u, \-\-user\fP. Added in 7.75.0.
372+.IP "\-\-basic"
373+(HTTP) Tells curl to use HTTP Basic authentication with the remote host. This is the
374+default and this option is usually pointless, unless you use it to override a
375+previously set option that sets a different authentication method (such as
376+\fI\-\-ntlm\fP, \fI\-\-digest\fP, or \fI\-\-negotiate\fP).
377+
378+Used together with \fI\-u, \-\-user\fP.
379+
380+Providing --basic multiple times has no extra effect.
381+
382+Example:
383+.nf
384+ curl -u name:password --basic https://example.com
385+.fi
386+
387+See also \fI\-\-proxy\-basic\fP.
388+.IP "\-\-ca\-native"
389+(TLS) Tells curl to use the CA store from the native operating system to verify the
390+peer. By default, curl otherwise uses a CA store provided in a single file or
391+directory, but when using this option it interfaces the operating system\(aqs
392+own vault.
393+
394+This option works for curl on Windows when built to use OpenSSL, wolfSSL
395+(added in 8.3.0) or GnuTLS (added in 8.5.0). When curl on Windows is built to
396+use Schannel, this feature is implied and curl then only uses the native CA
397+store.
398+
399+Providing --ca-native multiple times has no extra effect.
400+Disable it again with \-\-no-ca-native.
401+
402+Example:
403+.nf
404+ curl --ca-native https://example.com
405+.fi
406+
407+See also \fI\-\-cacert\fP, \fI\-\-capath\fP and \fI-k, \-\-insecure\fP. Added in 8.2.0.
408+.IP "\-\-cacert <file>"
409+(TLS) Tells curl to use the specified certificate file to verify the peer. The file
410+may contain multiple CA certificates. The certificate(s) must be in PEM
411+format. Normally curl is built to use a default file for this, so this option
412+is typically used to alter that default file.
413+
414+curl recognizes the environment variable named \(aqCURL_CA_BUNDLE\(aq if it is set
415+and the TLS backend is not Schannel, and uses the given path as a path to a CA
416+cert bundle. This option overrides that variable.
417+
418+The windows version of curl automatically looks for a CA certs file named
419+\(aqcurl\-ca\-bundle.crt\(aq, either in the same directory as curl.exe, or in the
420+Current Working Directory, or in any folder along your PATH.
421+
422+(iOS and macOS only) If curl is built against Secure Transport, then this
423+option is supported for backward compatibility with other SSL engines, but it
424+should not be set. If the option is not set, then curl uses the certificates
425+in the system and user Keychain to verify the peer, which is the preferred
426+method of verifying the peer\(aqs certificate chain.
427+
428+(Schannel only) This option is supported for Schannel in Windows 7 or later
429+(added in 7.60.0). This option is supported for backward compatibility with
430+other SSL engines; instead it is recommended to use Windows\(aq store of root
431+certificates (the default for Schannel).
432+
433+If --cacert is provided several times, the last set value is used.
434+
435+Example:
436+.nf
437+ curl --cacert CA-file.txt https://example.com
438+.fi
439+
440+See also \fI\-\-capath\fP and \fI-k, \-\-insecure\fP.
441+.IP "\-\-capath <dir>"
442+(TLS) Tells curl to use the specified certificate directory to verify the
443+peer. Multiple paths can be provided by separating them with ":" (e.g.
444+\&"path1:path2:path3"). The certificates must be in PEM format, and if curl is
445+built against OpenSSL, the directory must have been processed using the
446+c_rehash utility supplied with OpenSSL. Using \fI\-\-capath\fP can allow
447+OpenSSL\-powered curl to make SSL\-connections much more efficiently than using
448+\fI\-\-cacert\fP if the \fI\-\-cacert\fP file contains many CA certificates.
449+
450+If this option is set, the default capath value is ignored.
451+
452+If --capath is provided several times, the last set value is used.
453+
454+Example:
455+.nf
456+ curl --capath /local/directory https://example.com
457+.fi
458+
459+See also \fI\-\-cacert\fP and \fI-k, \-\-insecure\fP.
460+.IP "\-\-cert\-status"
461+(TLS) Tells curl to verify the status of the server certificate by using the
462+Certificate Status Request (aka. OCSP stapling) TLS extension.
463+
464+If this option is enabled and the server sends an invalid (e.g. expired)
465+response, if the response suggests that the server certificate has been
466+revoked, or no response at all is received, the verification fails.
467+
468+This is currently only implemented in the OpenSSL and GnuTLS backends.
469+
470+Providing --cert-status multiple times has no extra effect.
471+Disable it again with \-\-no-cert-status.
472+
473+Example:
474+.nf
475+ curl --cert-status https://example.com
476+.fi
477+
478+See also \fI\-\-pinnedpubkey\fP.
479+.IP "\-\-cert\-type <type>"
480+(TLS) Tells curl what type the provided client certificate is using. PEM, DER, ENG
481+and P12 are recognized types.
482+
483+The default type depends on the TLS backend and is usually PEM, however for
484+Secure Transport and Schannel it is P12. If \fI\-E, \-\-cert\fP is a pkcs11: URI then ENG is
485+the default type.
486+
487+If --cert-type is provided several times, the last set value is used.
488+
489+Example:
490+.nf
491+ curl --cert-type PEM --cert file https://example.com
492+.fi
493+
494+See also \fI-E, \-\-cert\fP, \fI\-\-key\fP and \fI\-\-key\-type\fP.
495+.IP "\-E, \-\-cert <certificate[:password]>"
496+(TLS) Tells curl to use the specified client certificate file when getting a file
497+with HTTPS, FTPS or another SSL\-based protocol. The certificate must be in
498+PKCS#12 format if using Secure Transport, or PEM format if using any other
499+engine. If the optional password is not specified, it is queried for on
500+the terminal. Note that this option assumes a certificate file that is the
501+private key and the client certificate concatenated. See \fI\-E, \-\-cert\fP and \fI\-\-key\fP to
502+specify them independently.
503+
504+In the <certificate> portion of the argument, you must escape the character
505+\&":" as "\\:" so that it is not recognized as the password delimiter. Similarly,
506+you must escape the double quote character as \\" so that it is not recognized
507+as an escape character.
508+
509+If curl is built against OpenSSL library, and the engine pkcs11 is available,
510+then a PKCS#11 URI (RFC 7512) can be used to specify a certificate located in
511+a PKCS#11 device. A string beginning with "pkcs11:" is interpreted as a
512+PKCS#11 URI. If a PKCS#11 URI is provided, then the \fI\-\-engine\fP option is set as
513+\&"pkcs11" if none was provided and the \fI\-\-cert\-type\fP option is set as "ENG" if
514+none was provided.
515+
516+(iOS and macOS only) If curl is built against Secure Transport, then the
517+certificate string can either be the name of a certificate/private key in the
518+system or user keychain, or the path to a PKCS#12\-encoded certificate and
519+private key. If you want to use a file from the current directory, please
520+precede it with "./" prefix, in order to avoid confusion with a nickname.
521+
522+(Schannel only) Client certificates must be specified by a path expression to
523+a certificate store. (Loading \fIPFX\fP is not supported; you can import it to a
524+store first). You can use "<store location>\\<store name>\\<thumbprint>" to
525+refer to a certificate in the system certificates store, for example,
526+\fI"CurrentUser\\MY\\934a7ac6f8a5d579285a74fa61e19f23ddfe8d7a"\fP. Thumbprint is
527+usually a SHA\-1 hex string which you can see in certificate details. Following
528+store locations are supported: \fICurrentUser\fP, \fILocalMachine\fP,
529+\fICurrentService\fP, \fIServices\fP, \fICurrentUserGroupPolicy\fP,
530+\fILocalMachineGroupPolicy\fP and \fILocalMachineEnterprise\fP.
531+
532+If --cert is provided several times, the last set value is used.
533+
534+Example:
535+.nf
536+ curl --cert certfile --key keyfile https://example.com
537+.fi
538+
539+See also \fI\-\-cert\-type\fP, \fI\-\-key\fP and \fI\-\-key\-type\fP.
540+.IP "\-\-ciphers <list of ciphers>"
541+(TLS) Specifies which ciphers to use in the connection. The list of ciphers must
542+specify valid ciphers. Read up on SSL cipher list details on this URL:
543+
544+https://curl.se/docs/ssl\-ciphers.html
545+
546+If --ciphers is provided several times, the last set value is used.
547+
548+Example:
549+.nf
550+ curl --ciphers ECDHE-ECDSA-AES256-CCM8 https://example.com
551+.fi
552+
553+See also \fI\-\-tlsv1.3\fP, \fI\-\-tls13\-ciphers\fP and \fI\-\-proxy\-ciphers\fP.
554+.IP "\-\-compressed\-ssh"
555+(SCP SFTP) Enables built\-in SSH compression.
556+This is a request, not an order; the server may or may not do it.
557+
558+Providing --compressed-ssh multiple times has no extra effect.
559+Disable it again with \-\-no-compressed-ssh.
560+
561+Example:
562+.nf
563+ curl --compressed-ssh sftp://example.com/
564+.fi
565+
566+See also \fI\-\-compressed\fP. Added in 7.56.0.
567+.IP "\-\-compressed"
568+(HTTP) Request a compressed response using one of the algorithms curl supports, and
569+automatically decompress the content.
570+
571+Response headers are not modified when saved, so if they are "interpreted"
572+separately again at a later point they might appear to be saying that the
573+content is (still) compressed; while in fact it has already been decompressed.
574+
575+If this option is used and the server sends an unsupported encoding, curl
576+reports an error. This is a request, not an order; the server may or may not
577+deliver data compressed.
578+
579+Providing --compressed multiple times has no extra effect.
580+Disable it again with \-\-no-compressed.
581+
582+Example:
583+.nf
584+ curl --compressed https://example.com
585+.fi
586+
587+See also \fI\-\-compressed\-ssh\fP.
588+.IP "\-K, \-\-config <file>"
589+Specify a text file to read curl arguments from. The command line arguments
590+found in the text file are used as if they were provided on the command
591+line.
592+
593+Options and their parameters must be specified on the same line in the file,
594+separated by whitespace, colon, or the equals sign. Long option names can
595+optionally be given in the config file without the initial double dashes and
596+if so, the colon or equals characters can be used as separators. If the option
597+is specified with one or two dashes, there can be no colon or equals character
598+between the option and its parameter.
599+
600+If the parameter contains whitespace or starts with a colon (:) or equals sign
601+(=), it must be specified enclosed within double quotes ("). Within double
602+quotes the following escape sequences are available: \\\\, \\", \\t, \\n, \\r and
603+\\v. A backslash preceding any other letter is ignored.
604+
605+If the first non\-blank column of a config line is a \(aq#\(aq character, that line
606+is treated as a comment.
607+
608+Only write one option per physical line in the config file. A single line is
609+required to be no more than 10 megabytes (since 8.2.0).
610+
611+Specify the filename to \fI\-K, \-\-config\fP as \(aq\-\(aq to make curl read the file from stdin.
612+
613+Note that to be able to specify a URL in the config file, you need to specify
614+it using the \fI\-\-url\fP option, and not by simply writing the URL on its own
615+line. So, it could look similar to this:
616+.nf
617+
618+url = "https://curl.se/docs/"
619+
620+# \--\- Example file \--\-
621+# this is a comment
622+url = "example.com"
623+output = "curlhere.html"
624+user\-agent = "superagent/1.0"
625+
626+# and fetch another URL too
627+url = "example.com/docs/manpage.html"
628+-O
629+referer = "http://nowhereatall.example.com/"
630+# \--\- End of example file \--\-
631+.fi
632+
633+When curl is invoked, it (unless \fI\-q, \-\-disable\fP is used) checks for a default
634+config file and uses it if found, even when \fI\-K, \-\-config\fP is used. The default
635+config file is checked for in the following places in this order:
636+
637+1) \fB"$CURL_HOME/.curlrc"\fP
638+
639+2) \fB"$XDG_CONFIG_HOME/curlrc"\fP (Added in 7.73.0)
640+
641+3) \fB"$HOME/.curlrc"\fP
642+
643+4) Windows: \fB"%USERPROFILE%\\.curlrc"\fP
644+
645+5) Windows: \fB"%APPDATA%\\.curlrc"\fP
646+
647+6) Windows: \fB"%USERPROFILE%\\Application Data\\.curlrc"\fP
648+
649+7) Non\-Windows: use getpwuid to find the home directory
650+
651+8) On Windows, if it finds no \fI.curlrc\fP file in the sequence described above, it
652+checks for one in the same dir the curl executable is placed.
653+
654+On Windows two filenames are checked per location: \fI.curlrc\fP and \fI_curlrc\fP,
655+preferring the former. Older versions on Windows checked for \fI_curlrc\fP only.
656+
657+--config can be used several times in a command line
658+
659+Example:
660+.nf
661+ curl --config file.txt https://example.com
662+.fi
663+
664+See also \fI-q, \-\-disable\fP.
665+.IP "\-\-connect\-timeout <fractional seconds>"
666+Maximum time in seconds that you allow curl\(aqs connection to take. This only
667+limits the connection phase, so if curl connects within the given period it
668+continues \- if not it exits.
669+
670+This option accepts decimal values. The decimal value needs
671+to be provided using a dot (.) as decimal separator \- not the local version
672+even if it might be using another separator.
673+
674+The connection phase is considered complete when the DNS lookup and requested
675+TCP, TLS or QUIC handshakes are done.
676+
677+If --connect-timeout is provided several times, the last set value is used.
678+
679+Examples:
680+.nf
681+ curl --connect-timeout 20 https://example.com
682+ curl --connect-timeout 3.14 https://example.com
683+.fi
684+
685+See also \fI-m, \-\-max\-time\fP.
686+.IP "\-\-connect\-to <HOST1:PORT1:HOST2:PORT2>"
687+For a request to the given "HOST1:PORT1" pair, connect to "HOST2:PORT2"
688+instead. This option is suitable to direct requests at a specific server,
689+e.g. at a specific cluster node in a cluster of servers. This option is only
690+used to establish the network connection. It does NOT affect the hostname/port
691+that is used for TLS/SSL (e.g. SNI, certificate verification) or for the
692+application protocols. "HOST1" and "PORT1" may be the empty string, meaning
693+\&"any host/port". "HOST2" and "PORT2" may also be the empty string, meaning
694+\&"use the request\(aqs original host/port".
695+
696+A hostname specified to this option is compared as a string, so it needs to
697+match the name used in request URL. It can be either numerical such as
698+\&"127.0.0.1" or the full host name such as "example.org".
699+
700+--connect-to can be used several times in a command line
701+
702+Example:
703+.nf
704+ curl --connect-to example.com:443:example.net:8443 https://example.com
705+.fi
706+
707+See also \fI\-\-resolve\fP and \fI-H, \-\-header\fP.
708+.IP "\-C, \-\-continue\-at <offset>"
709+Continue/Resume a previous file transfer at the given offset. The given offset
710+is the exact number of bytes that are skipped, counting from the beginning
711+of the source file before it is transferred to the destination. If used with
712+uploads, the FTP server command SIZE is not used by curl.
713+
714+Use "\-C \-" to tell curl to automatically find out where/how to resume the
715+transfer. It then uses the given output/input files to figure that out.
716+
717+If --continue-at is provided several times, the last set value is used.
718+
719+Examples:
720+.nf
721+ curl -C - https://example.com
722+ curl -C 400 https://example.com
723+.fi
724+
725+See also \fI-r, \-\-range\fP.
726+.IP "\-c, \-\-cookie\-jar <filename>"
727+(HTTP) Specify to which file you want curl to write all cookies after a completed
728+operation. Curl writes all cookies from its in\-memory cookie storage to the
729+given file at the end of operations. If no cookies are known, no data is
730+written. The file is created using the Netscape cookie file format. If you set
731+the file name to a single dash, "\-", the cookies are written to stdout.
732+
733+The file specified with \fI\-c, \-\-cookie\-jar\fP is only used for output. No cookies are
734+read from the file. To read cookies, use the \fI\-b, \-\-cookie\fP option. Both options
735+can specify the same file.
736+
737+This command line option activates the cookie engine that makes curl record
738+and use cookies. The \fI\-b, \-\-cookie\fP option also activates it.
739+
740+If the cookie jar cannot be created or written to, the whole curl operation
741+does not fail or even report an error clearly. Using \fI\-v, \-\-verbose\fP gets a warning
742+displayed, but that is the only visible feedback you get about this possibly
743+lethal situation.
744+
745+If --cookie-jar is provided several times, the last set value is used.
746+
747+Examples:
748+.nf
749+ curl -c store-here.txt https://example.com
750+ curl -c store-here.txt -b read-these https://example.com
751+.fi
752+
753+See also \fI-b, \-\-cookie\fP.
754+.IP "\-b, \-\-cookie <data|filename>"
755+(HTTP) Pass the data to the HTTP server in the Cookie header. It is supposedly the
756+data previously received from the server in a "Set\-Cookie:" line. The data
757+should be in the format "NAME1=VALUE1; NAME2=VALUE2". This makes curl use the
758+cookie header with this content explicitly in all outgoing request(s). If
759+multiple requests are done due to authentication, followed redirects or
760+similar, they all get this cookie passed on.
761+
762+If no \(aq=\(aq symbol is used in the argument, it is instead treated as a filename
763+to read previously stored cookie from. This option also activates the cookie
764+engine which makes curl record incoming cookies, which may be handy if you are
765+using this in combination with the \fI\-L, \-\-location\fP option or do multiple URL
766+transfers on the same invoke.
767+
768+If the file name is exactly a minus ("\-"), curl instead reads the contents from
769+stdin. If the file name is an empty string ("") and is the only cookie input,
770+curl will activate the cookie engine without any cookies.
771+
772+The file format of the file to read cookies from should be plain HTTP headers
773+(Set\-Cookie style) or the Netscape/Mozilla cookie file format.
774+
775+The file specified with \fI\-b, \-\-cookie\fP is only used as input. No cookies are written
776+to the file. To store cookies, use the \fI\-c, \-\-cookie\-jar\fP option.
777+
778+If you use the Set\-Cookie file format and do not specify a domain then the
779+cookie is not sent since the domain never matches. To address this, set a
780+domain in Set\-Cookie line (doing that includes subdomains) or preferably: use
781+the Netscape format.
782+
783+Users often want to both read cookies from a file and write updated cookies
784+back to a file, so using both \fI\-b, \-\-cookie\fP and \fI\-c, \-\-cookie\-jar\fP in the same command
785+line is common.
786+
787+If curl is built with PSL (\fBPublic Suffix List\fP) support, it detects and
788+discards cookies that are specified for such suffix domains that should not be
789+allowed to have cookies. If curl is \fInot\fP built with PSL support, it has no
790+ability to stop super cookies.
791+
792+--cookie can be used several times in a command line
793+
794+Examples:
795+.nf
796+ curl -b "" https://example.com
797+ curl -b cookiefile https://example.com
798+ curl -b cookiefile -c cookiefile https://example.com
799+.fi
800+
801+See also \fI-c, \-\-cookie\-jar\fP and \fI-j, \-\-junk\-session\-cookies\fP.
802+.IP "\-\-create\-dirs"
803+When used in conjunction with the \fI\-o, \-\-output\fP option, curl creates the necessary
804+local directory hierarchy as needed. This option creates the directories
805+mentioned with the \fI\-o, \-\-output\fP option combined with the path possibly set with
806+\fI\-\-output\-dir\fP. If the combined output file name uses no directory, or if the
807+directories it mentions already exist, no directories are created.
808+
809+Created directories are made with mode 0750 on unix style file systems.
810+
811+To create remote directories when using FTP or SFTP, try \fI\-\-ftp\-create\-dirs\fP.
812+
813+Providing --create-dirs multiple times has no extra effect.
814+Disable it again with \-\-no-create-dirs.
815+
816+Example:
817+.nf
818+ curl --create-dirs --output local/dir/file https://example.com
819+.fi
820+
821+See also \fI\-\-ftp\-create\-dirs\fP and \fI\-\-output\-dir\fP.
822+.IP "\-\-create\-file\-mode <mode>"
823+(SFTP SCP FILE) When curl is used to create files remotely using one of the supported
824+protocols, this option allows the user to set which \(aqmode\(aq to set on the file
825+at creation time, instead of the default 0644.
826+
827+This option takes an octal number as argument.
828+
829+If --create-file-mode is provided several times, the last set value is used.
830+
831+Example:
832+.nf
833+ curl --create-file-mode 0777 -T localfile sftp://example.com/new
834+.fi
835+
836+See also \fI\-\-ftp\-create\-dirs\fP. Added in 7.75.0.
837+.IP "\-\-crlf"
838+(FTP SMTP) Convert line feeds to carriage return plus line feeds in upload. Useful for
839+\fBMVS (OS/390)\fP.
840+
841+(SMTP added in 7.40.0)
842+
843+Providing --crlf multiple times has no extra effect.
844+Disable it again with \-\-no-crlf.
845+
846+Example:
847+.nf
848+ curl --crlf -T file ftp://example.com/
849+.fi
850+
851+See also \fI-B, \-\-use\-ascii\fP.
852+.IP "\-\-crlfile <file>"
853+(TLS) Provide a file using PEM format with a Certificate Revocation List that may
854+specify peer certificates that are to be considered revoked.
855+
856+If --crlfile is provided several times, the last set value is used.
857+
858+Example:
859+.nf
860+ curl --crlfile rejects.txt https://example.com
861+.fi
862+
863+See also \fI\-\-cacert\fP and \fI\-\-capath\fP.
864+.IP "\-\-curves <algorithm list>"
865+(TLS) Tells curl to request specific curves to use during SSL session establishment
866+according to RFC 8422, 5.1. Multiple algorithms can be provided by separating
867+them with ":" (e.g. "X25519:P\-521"). The parameter is available identically in
868+the OpenSSL "s_client" and "s_server" utilities.
869+
870+\fI\-\-curves\fP allows a OpenSSL powered curl to make SSL\-connections with exactly
871+the (EC) curve requested by the client, avoiding nontransparent client/server
872+negotiations.
873+
874+If this option is set, the default curves list built into OpenSSL are ignored.
875+
876+If --curves is provided several times, the last set value is used.
877+
878+Example:
879+.nf
880+ curl --curves X25519 https://example.com
881+.fi
882+
883+See also \fI\-\-ciphers\fP. Added in 7.73.0.
884+.IP "\-\-data\-ascii <data>"
885+(HTTP) This is just an alias for \fI\-d, \-\-data\fP.
886+
887+--data-ascii can be used several times in a command line
888+
889+Example:
890+.nf
891+ curl --data-ascii @file https://example.com
892+.fi
893+
894+See also \fI\-\-data\-binary\fP, \fI\-\-data\-raw\fP and \fI\-\-data\-urlencode\fP.
895+.IP "\-\-data\-binary <data>"
896+(HTTP) This posts data exactly as specified with no extra processing whatsoever.
897+
898+If you start the data with the letter @, the rest should be a filename. Data
899+is posted in a similar manner as \fI\-d, \-\-data\fP does, except that newlines and
900+carriage returns are preserved and conversions are never done.
901+
902+Like \fI\-d, \-\-data\fP the default content\-type sent to the server is
903+application/x\-www\-form\-urlencoded. If you want the data to be treated as
904+arbitrary binary data by the server then set the content\-type to octet\-stream:
905+-H "Content\-Type: application/octet\-stream".
906+
907+If this option is used several times, the ones following the first append
908+data as described in \fI\-d, \-\-data\fP.
909+
910+--data-binary can be used several times in a command line
911+
912+Example:
913+.nf
914+ curl --data-binary @filename https://example.com
915+.fi
916+
917+See also \fI\-\-data\-ascii\fP.
918+.IP "\-\-data\-raw <data>"
919+(HTTP) This posts data similarly to \fI\-d, \-\-data\fP but without the special
920+interpretation of the @ character.
921+
922+--data-raw can be used several times in a command line
923+
924+Examples:
925+.nf
926+ curl --data-raw "hello" https://example.com
927+ curl --data-raw "@at@at@" https://example.com
928+.fi
929+
930+See also \fI-d, \-\-data\fP.
931+.IP "\-\-data\-urlencode <data>"
932+(HTTP) This posts data, similar to the other \fI\-d, \-\-data\fP options with the exception
933+that this performs URL\-encoding.
934+
935+To be CGI\-compliant, the <data> part should begin with a \fIname\fP followed
936+by a separator and a content specification. The <data> part can be passed to
937+curl using one of the following syntaxes:
938+.RS
939+.IP content
940+This makes curl URL\-encode the content and pass that on. Just be careful
941+so that the content does not contain any = or @ symbols, as that makes
942+the syntax match one of the other cases below!
943+.IP =content
944+This makes curl URL\-encode the content and pass that on. The preceding =
945+symbol is not included in the data.
946+.IP name=content
947+This makes curl URL\-encode the content part and pass that on. Note that
948+the name part is expected to be URL\-encoded already.
949+.IP @filename
950+This makes curl load data from the given file (including any newlines),
951+URL\-encode that data and pass it on in the POST.
952+.IP name@filename
953+This makes curl load data from the given file (including any newlines),
954+URL\-encode that data and pass it on in the POST. The name part gets an equal
955+sign appended, resulting in \fIname=urlencoded\-file\-content\fP. Note that the
956+name is expected to be URL\-encoded already.
957+.RE
958+.IP
959+
960+--data-urlencode can be used several times in a command line
961+
962+Examples:
963+.nf
964+ curl --data-urlencode name=val https://example.com
965+ curl --data-urlencode =encodethis https://example.com
966+ curl --data-urlencode name@file https://example.com
967+ curl --data-urlencode @fileonly https://example.com
968+.fi
969+
970+See also \fI-d, \-\-data\fP and \fI\-\-data\-raw\fP.
971+.IP "\-d, \-\-data <data>"
972+(HTTP MQTT) Sends the specified data in a POST request to the HTTP server, in the same way
973+that a browser does when a user has filled in an HTML form and presses the
974+submit button. This makes curl pass the data to the server using the
975+content\-type application/x\-www\-form\-urlencoded. Compare to \fI\-F, \-\-form\fP.
976+
977+\fI\-\-data\-raw\fP is almost the same but does not have a special interpretation of
978+the @ character. To post data purely binary, you should instead use the
979+\fI\-\-data\-binary\fP option. To URL\-encode the value of a form field you may use
980+\fI\-\-data\-urlencode\fP.
981+
982+If any of these options is used more than once on the same command line, the
983+data pieces specified are merged with a separating &\-symbol. Thus, using
984+\(aq\-d name=daniel \-d skill=lousy\(aq would generate a post chunk that looks like
985+\(aqname=daniel&skill=lousy\(aq.
986+
987+If you start the data with the letter @, the rest should be a file name to
988+read the data from, or \- if you want curl to read the data from stdin. Posting
989+data from a file named \(aqfoobar\(aq would thus be done with \fI\-d, \-\-data\fP @foobar. When
990+\fI\-d, \-\-data\fP is told to read from a file like that, carriage returns and newlines
991+are stripped out. If you do not want the @ character to have a special
992+interpretation use \fI\-\-data\-raw\fP instead.
993+
994+The data for this option is passed on to the server exactly as provided on the
995+command line. curl does not convert, change or improve it. It is up to the
996+user to provide the data in the correct form.
997+
998+--data can be used several times in a command line
999+
1000+Examples:
1001+.nf
1002+ curl -d "name=curl" https://example.com
1003+ curl -d "name=curl" -d "tool=cmdline" https://example.com
1004+ curl -d @filename https://example.com
1005+.fi
1006+
1007+See also \fI\-\-data\-binary\fP, \fI\-\-data\-urlencode\fP and \fI\-\-data\-raw\fP. This option is mutually exclusive to \fI-F, \-\-form\fP and \fI-I, \-\-head\fP and \fI-T, \-\-upload\-file\fP.
1008+.IP "\-\-delegation <LEVEL>"
1009+(GSS/kerberos) Set LEVEL to tell the server what it is allowed to delegate when it
1010+comes to user credentials.
1011+.RS
1012+.IP none
1013+Do not allow any delegation.
1014+.IP policy
1015+Delegates if and only if the OK\-AS\-DELEGATE flag is set in the Kerberos
1016+service ticket, which is a matter of realm policy.
1017+.IP always
1018+Unconditionally allow the server to delegate.
1019+.RE
1020+.IP
1021+
1022+If --delegation is provided several times, the last set value is used.
1023+
1024+Example:
1025+.nf
1026+ curl --delegation "none" https://example.com
1027+.fi
1028+
1029+See also \fI-k, \-\-insecure\fP and \fI\-\-ssl\fP.
1030+.IP "\-\-digest"
1031+(HTTP) Enables HTTP Digest authentication. This is an authentication scheme that
1032+prevents the password from being sent over the wire in clear text. Use this in
1033+combination with the normal \fI\-u, \-\-user\fP option to set user name and password.
1034+
1035+Providing --digest multiple times has no extra effect.
1036+Disable it again with \-\-no-digest.
1037+
1038+Example:
1039+.nf
1040+ curl -u name:password --digest https://example.com
1041+.fi
1042+
1043+See also \fI-u, \-\-user\fP, \fI\-\-proxy\-digest\fP and \fI\-\-anyauth\fP. This option is mutually exclusive to \fI\-\-basic\fP and \fI\-\-ntlm\fP and \fI\-\-negotiate\fP.
1044+.IP "\-\-disable\-eprt"
1045+(FTP) Tell curl to disable the use of the EPRT and LPRT commands when doing active
1046+FTP transfers. Curl normally first attempts to use EPRT before using PORT, but
1047+with this option, it uses PORT right away. EPRT is an extension to the
1048+original FTP protocol, and does not work on all servers, but enables more
1049+functionality in a better way than the traditional PORT command.
1050+
1051+-\-eprt can be used to explicitly enable EPRT again and \--no\-eprt is an alias
1052+for \fI\-\-disable\-eprt\fP.
1053+
1054+If the server is accessed using IPv6, this option has no effect as EPRT is
1055+necessary then.
1056+
1057+Disabling EPRT only changes the active behavior. If you want to switch to
1058+passive mode you need to not use \fI\-P, \-\-ftp\-port\fP or force it with \fI\-\-ftp\-pasv\fP.
1059+
1060+Providing --disable-eprt multiple times has no extra effect.
1061+Disable it again with \-\-no-disable-eprt.
1062+
1063+Example:
1064+.nf
1065+ curl --disable-eprt ftp://example.com/
1066+.fi
1067+
1068+See also \fI\-\-disable\-epsv\fP and \fI-P, \-\-ftp\-port\fP.
1069+.IP "\-\-disable\-epsv"
1070+(FTP) Tell curl to disable the use of the EPSV command when doing passive FTP
1071+transfers. Curl normally first attempts to use EPSV before PASV, but with this
1072+option, it does not try EPSV.
1073+
1074+-\-epsv can be used to explicitly enable EPSV again and \--no\-epsv is an alias
1075+for \fI\-\-disable\-epsv\fP.
1076+
1077+If the server is an IPv6 host, this option has no effect as EPSV is necessary
1078+then.
1079+
1080+Disabling EPSV only changes the passive behavior. If you want to switch to
1081+active mode you need to use \fI\-P, \-\-ftp\-port\fP.
1082+
1083+Providing --disable-epsv multiple times has no extra effect.
1084+Disable it again with \-\-no-disable-epsv.
1085+
1086+Example:
1087+.nf
1088+ curl --disable-epsv ftp://example.com/
1089+.fi
1090+
1091+See also \fI\-\-disable\-eprt\fP and \fI-P, \-\-ftp\-port\fP.
1092+.IP "\-q, \-\-disable"
1093+If used as the \fBfirst\fP parameter on the command line, the \fIcurlrc\fP config
1094+file is not read or used. See the \fI\-K, \-\-config\fP for details on the default config
1095+file search path.
1096+
1097+Prior to 7.50.0 curl supported the short option name \fIq\fP but not the long
1098+option name \fIdisable\fP.
1099+
1100+Providing --disable multiple times has no extra effect.
1101+Disable it again with \-\-no-disable.
1102+
1103+Example:
1104+.nf
1105+ curl -q https://example.com
1106+.fi
1107+
1108+See also \fI-K, \-\-config\fP.
1109+.IP "\-\-disallow\-username\-in\-url"
1110+This tells curl to exit if passed a URL containing a username. This is probably
1111+most useful when the URL is being provided at runtime or similar.
1112+
1113+Providing --disallow-username-in-url multiple times has no extra effect.
1114+Disable it again with \-\-no-disallow-username-in-url.
1115+
1116+Example:
1117+.nf
1118+ curl --disallow-username-in-url https://example.com
1119+.fi
1120+
1121+See also \fI\-\-proto\fP. Added in 7.61.0.
1122+.IP "\-\-dns\-interface <interface>"
1123+(DNS) Tell curl to send outgoing DNS requests through <interface>. This option is a
1124+counterpart to \fI\-\-interface\fP (which does not affect DNS). The supplied string
1125+must be an interface name (not an address).
1126+
1127+If --dns-interface is provided several times, the last set value is used.
1128+
1129+Example:
1130+.nf
1131+ curl --dns-interface eth0 https://example.com
1132+.fi
1133+
1134+See also \fI\-\-dns\-ipv4\-addr\fP and \fI\-\-dns\-ipv6\-addr\fP. \fI\-\-dns\-interface\fP requires that the underlying libcurl was built to support c-ares.
1135+.IP "\-\-dns\-ipv4\-addr <address>"
1136+(DNS) Tell curl to bind to a specific IP address when making IPv4 DNS requests, so
1137+that the DNS requests originate from this address. The argument should be a
1138+single IPv4 address.
1139+
1140+If --dns-ipv4-addr is provided several times, the last set value is used.
1141+
1142+Example:
1143+.nf
1144+ curl --dns-ipv4-addr 10.1.2.3 https://example.com
1145+.fi
1146+
1147+See also \fI\-\-dns\-interface\fP and \fI\-\-dns\-ipv6\-addr\fP. \fI\-\-dns\-ipv4\-addr\fP requires that the underlying libcurl was built to support c-ares.
1148+.IP "\-\-dns\-ipv6\-addr <address>"
1149+(DNS) Tell curl to bind to a specific IP address when making IPv6 DNS requests, so
1150+that the DNS requests originate from this address. The argument should be a
1151+single IPv6 address.
1152+
1153+If --dns-ipv6-addr is provided several times, the last set value is used.
1154+
1155+Example:
1156+.nf
1157+ curl --dns-ipv6-addr 2a04:4e42::561 https://example.com
1158+.fi
1159+
1160+See also \fI\-\-dns\-interface\fP and \fI\-\-dns\-ipv4\-addr\fP. \fI\-\-dns\-ipv6\-addr\fP requires that the underlying libcurl was built to support c-ares.
1161+.IP "\-\-dns\-servers <addresses>"
1162+(DNS) Set the list of DNS servers to be used instead of the system default.
1163+The list of IP addresses should be separated with commas. Port numbers
1164+may also optionally be given as \fI:<port\-number>\fP after each IP
1165+address.
1166+
1167+If --dns-servers is provided several times, the last set value is used.
1168+
1169+Example:
1170+.nf
1171+ curl --dns-servers 192.168.0.1,192.168.0.2 https://example.com
1172+.fi
1173+
1174+See also \fI\-\-dns\-interface\fP and \fI\-\-dns\-ipv4\-addr\fP. \fI\-\-dns\-servers\fP requires that the underlying libcurl was built to support c-ares.
1175+.IP "\-\-doh\-cert\-status"
1176+Same as \fI\-\-cert\-status\fP but used for DoH (DNS\-over\-HTTPS).
1177+
1178+Providing --doh-cert-status multiple times has no extra effect.
1179+Disable it again with \-\-no-doh-cert-status.
1180+
1181+Example:
1182+.nf
1183+ curl --doh-cert-status --doh-url https://doh.example https://example.com
1184+.fi
1185+
1186+See also \fI\-\-doh\-insecure\fP. Added in 7.76.0.
1187+.IP "\-\-doh\-insecure"
1188+Same as \fI\-k, \-\-insecure\fP but used for DoH (DNS\-over\-HTTPS).
1189+
1190+Providing --doh-insecure multiple times has no extra effect.
1191+Disable it again with \-\-no-doh-insecure.
1192+
1193+Example:
1194+.nf
1195+ curl --doh-insecure --doh-url https://doh.example https://example.com
1196+.fi
1197+
1198+See also \fI\-\-doh\-url\fP. Added in 7.76.0.
1199+.IP "\-\-doh\-url <URL>"
1200+Specifies which DNS\-over\-HTTPS (DoH) server to use to resolve hostnames,
1201+instead of using the default name resolver mechanism. The URL must be HTTPS.
1202+
1203+Some SSL options that you set for your transfer also applies to DoH since the
1204+name lookups take place over SSL. However, the certificate verification
1205+settings are not inherited but are controlled separately via \fI\-\-doh\-insecure\fP
1206+and \fI\-\-doh\-cert\-status\fP.
1207+
1208+This option is unset if an empty string "" is used as the URL.
1209+(Added in 7.85.0)
1210+
1211+If --doh-url is provided several times, the last set value is used.
1212+
1213+Example:
1214+.nf
1215+ curl --doh-url https://doh.example https://example.com
1216+.fi
1217+
1218+See also \fI\-\-doh\-insecure\fP. Added in 7.62.0.
1219+.IP "\-D, \-\-dump\-header <filename>"
1220+(HTTP FTP) Write the received protocol headers to the specified file. If no headers are
1221+received, the use of this option creates an empty file.
1222+
1223+When used in FTP, the FTP server response lines are considered being "headers"
1224+and thus are saved there.
1225+
1226+Having multiple transfers in one set of operations (i.e. the URLs in one
1227+\fI\-:, \-\-next\fP clause), appends them to the same file, separated by a blank line.
1228+
1229+If --dump-header is provided several times, the last set value is used.
1230+
1231+Example:
1232+.nf
1233+ curl --dump-header store.txt https://example.com
1234+.fi
1235+
1236+See also \fI-o, \-\-output\fP.
1237+.IP "\-\-egd\-file <file>"
1238+(TLS) Deprecated option (added in 7.84.0). Prior to that it only had an effect on
1239+curl if built to use old versions of OpenSSL.
1240+
1241+Specify the path name to the Entropy Gathering Daemon socket. The socket is
1242+used to seed the random engine for SSL connections.
1243+
1244+If --egd-file is provided several times, the last set value is used.
1245+
1246+Example:
1247+.nf
1248+ curl --egd-file /random/here https://example.com
1249+.fi
1250+
1251+See also \fI\-\-random\-file\fP.
1252+.IP "\-\-engine <name>"
1253+(TLS) Select the OpenSSL crypto engine to use for cipher operations. Use \fI\-\-engine\fP
1254+list to print a list of build\-time supported engines. Note that not all (and
1255+possibly none) of the engines may be available at runtime.
1256+
1257+If --engine is provided several times, the last set value is used.
1258+
1259+Example:
1260+.nf
1261+ curl --engine flavor https://example.com
1262+.fi
1263+
1264+See also \fI\-\-ciphers\fP and \fI\-\-curves\fP.
1265+.IP "\-\-etag\-compare <file>"
1266+(HTTP) This option makes a conditional HTTP request for the specific ETag read
1267+from the given file by sending a custom If\-None\-Match header using the
1268+stored ETag.
1269+
1270+For correct results, make sure that the specified file contains only a
1271+single line with the desired ETag. An empty file is parsed as an empty
1272+ETag.
1273+
1274+Use the option \fI\-\-etag\-save\fP to first save the ETag from a response, and
1275+then use this option to compare against the saved ETag in a subsequent
1276+request.
1277+
1278+If --etag-compare is provided several times, the last set value is used.
1279+
1280+Example:
1281+.nf
1282+ curl --etag-compare etag.txt https://example.com
1283+.fi
1284+
1285+See also \fI\-\-etag\-save\fP and \fI-z, \-\-time\-cond\fP. Added in 7.68.0.
1286+.IP "\-\-etag\-save <file>"
1287+(HTTP) This option saves an HTTP ETag to the specified file. An ETag is a
1288+caching related header, usually returned in a response.
1289+
1290+If no ETag is sent by the server, an empty file is created.
1291+
1292+If --etag-save is provided several times, the last set value is used.
1293+
1294+Example:
1295+.nf
1296+ curl --etag-save storetag.txt https://example.com
1297+.fi
1298+
1299+See also \fI\-\-etag\-compare\fP. Added in 7.68.0.
1300+.IP "\-\-expect100\-timeout <seconds>"
1301+(HTTP) Maximum time in seconds that you allow curl to wait for a 100\-continue
1302+response when curl emits an Expects: 100\-continue header in its request. By
1303+default curl waits one second. This option accepts decimal values! When
1304+curl stops waiting, it continues as if the response has been received.
1305+
1306+The decimal value needs to provided using a dot (.) as decimal separator \- not
1307+the local version even if it might be using another separator.
1308+
1309+If --expect100-timeout is provided several times, the last set value is used.
1310+
1311+Example:
1312+.nf
1313+ curl --expect100-timeout 2.5 -T file https://example.com
1314+.fi
1315+
1316+See also \fI\-\-connect\-timeout\fP.
1317+.IP "\-\-fail\-early"
1318+Fail and exit on the first detected transfer error.
1319+
1320+When curl is used to do multiple transfers on the command line, it attempts to
1321+operate on each given URL, one by one. By default, it ignores errors if there
1322+are more URLs given and the last URL\(aqs success determines the error code curl
1323+returns. So early failures are "hidden" by subsequent successful transfers.
1324+
1325+Using this option, curl instead returns an error on the first transfer that
1326+fails, independent of the amount of URLs that are given on the command
1327+line. This way, no transfer failures go undetected by scripts and similar.
1328+
1329+This option does not imply \fI\-f, \-\-fail\fP, which causes transfers to fail due to the
1330+server\(aqs HTTP status code. You can combine the two options, however note \fI\-f, \-\-fail\fP
1331+is not global and is therefore contained by \fI\-:, \-\-next\fP.
1332+
1333+This option is global and does not need to be specified for each use of --next.
1334+
1335+Providing --fail-early multiple times has no extra effect.
1336+Disable it again with \-\-no-fail-early.
1337+
1338+Example:
1339+.nf
1340+ curl --fail-early https://example.com https://two.example
1341+.fi
1342+
1343+See also \fI-f, \-\-fail\fP and \fI\-\-fail\-with\-body\fP. Added in 7.52.0.
1344+.IP "\-\-fail\-with\-body"
1345+(HTTP) Return an error on server errors where the HTTP response code is 400 or
1346+greater). In normal cases when an HTTP server fails to deliver a document, it
1347+returns an HTML document stating so (which often also describes why and
1348+more). This flag allows curl to output and save that content but also to
1349+return error 22.
1350+
1351+This is an alternative option to \fI\-f, \-\-fail\fP which makes curl fail for the same
1352+circumstances but without saving the content.
1353+
1354+Providing --fail-with-body multiple times has no extra effect.
1355+Disable it again with \-\-no-fail-with-body.
1356+
1357+Example:
1358+.nf
1359+ curl --fail-with-body https://example.com
1360+.fi
1361+
1362+See also \fI-f, \-\-fail\fP and \fI\-\-fail\-early\fP. This option is mutually exclusive to \fI-f, \-\-fail\fP. Added in 7.76.0.
1363+.IP "\-f, \-\-fail"
1364+(HTTP) Fail fast with no output at all on server errors. This is useful to enable
1365+scripts and users to better deal with failed attempts. In normal cases when an
1366+HTTP server fails to deliver a document, it returns an HTML document stating
1367+so (which often also describes why and more). This flag prevents curl from
1368+outputting that and return error 22.
1369+
1370+This method is not fail\-safe and there are occasions where non\-successful
1371+response codes slip through, especially when authentication is involved
1372+(response codes 401 and 407).
1373+
1374+Providing --fail multiple times has no extra effect.
1375+Disable it again with \-\-no-fail.
1376+
1377+Example:
1378+.nf
1379+ curl --fail https://example.com
1380+.fi
1381+
1382+See also \fI\-\-fail\-with\-body\fP and \fI\-\-fail\-early\fP. This option is mutually exclusive to \fI\-\-fail\-with\-body\fP.
1383+.IP "\-\-false\-start"
1384+(TLS) Tells curl to use false start during the TLS handshake. False start is a mode
1385+where a TLS client starts sending application data before verifying the
1386+server\(aqs Finished message, thus saving a round trip when performing a full
1387+handshake.
1388+
1389+This is currently only implemented in the Secure Transport (on iOS 7.0 or
1390+later, or OS X 10.9 or later) backend.
1391+
1392+Providing --false-start multiple times has no extra effect.
1393+Disable it again with \-\-no-false-start.
1394+
1395+Example:
1396+.nf
1397+ curl --false-start https://example.com
1398+.fi
1399+
1400+See also \fI\-\-tcp\-fastopen\fP.
1401+.IP "\-\-form\-escape"
1402+(HTTP) Tells curl to pass on names of multipart form fields and files using
1403+backslash\-escaping instead of percent\-encoding.
1404+
1405+If --form-escape is provided several times, the last set value is used.
1406+
1407+Example:
1408+.nf
1409+ curl --form-escape -F 'field\\name=curl' -F 'file=@load"this' https://example.com
1410+.fi
1411+
1412+See also \fI-F, \-\-form\fP. Added in 7.81.0.
1413+.IP "\-\-form\-string <name=string>"
1414+(HTTP SMTP IMAP) Similar to \fI\-F, \-\-form\fP except that the value string for the named parameter is used
1415+literally. Leading \(aq@\(aq and \(aq<\(aq characters, and the \(aq;type=\(aq string in
1416+the value have no special meaning. Use this in preference to \fI\-F, \-\-form\fP if
1417+there is any possibility that the string value may accidentally trigger the
1418+\(aq@\(aq or \(aq<\(aq features of \fI\-F, \-\-form\fP.
1419+
1420+--form-string can be used several times in a command line
1421+
1422+Example:
1423+.nf
1424+ curl --form-string "data" https://example.com
1425+.fi
1426+
1427+See also \fI-F, \-\-form\fP.
1428+.IP "\-F, \-\-form <name=content>"
1429+(HTTP SMTP IMAP) For HTTP protocol family, this lets curl emulate a filled\-in form in which a
1430+user has pressed the submit button. This causes curl to POST data using the
1431+Content\-Type multipart/form\-data according to RFC 2388.
1432+
1433+For SMTP and IMAP protocols, this is the means to compose a multipart mail
1434+message to transmit.
1435+
1436+This enables uploading of binary files etc. To force the \(aqcontent\(aq part to be
1437+a file, prefix the file name with an @ sign. To just get the content part from
1438+a file, prefix the file name with the symbol <. The difference between @ and <
1439+is then that @ makes a file get attached in the post as a file upload, while
1440+the < makes a text field and just get the contents for that text field from a
1441+file.
1442+
1443+Tell curl to read content from stdin instead of a file by using \- as
1444+filename. This goes for both @ and < constructs. When stdin is used, the
1445+contents is buffered in memory first by curl to determine its size and allow a
1446+possible resend. Defining a part\(aqs data from a named non\-regular file (such as
1447+a named pipe or similar) is not subject to buffering and is instead read at
1448+transmission time; since the full size is unknown before the transfer starts,
1449+such data is sent as chunks by HTTP and rejected by IMAP.
1450+
1451+Example: send an image to an HTTP server, where \(aqprofile\(aq is the name of the
1452+form\-field to which the file \fBportrait.jpg\fP is the input:
1453+.nf
1454+
1455+curl \-F profile=@portrait.jpg https://example.com/upload.cgi
1456+.fi
1457+
1458+Example: send your name and shoe size in two text fields to the server:
1459+.nf
1460+
1461+curl \-F name=John \-F shoesize=11 https://example.com/
1462+.fi
1463+
1464+Example: send your essay in a text field to the server. Send it as a plain
1465+text field, but get the contents for it from a local file:
1466+.nf
1467+
1468+curl \-F "story=<hugefile.txt" https://example.com/
1469+.fi
1470+
1471+You can also tell curl what Content\-Type to use by using \(aqtype=\(aq, in a manner
1472+similar to:
1473+.nf
1474+
1475+curl \-F "web=@index.html;type=text/html" example.com
1476+.fi
1477+
1478+or
1479+.nf
1480+
1481+curl \-F "name=daniel;type=text/foo" example.com
1482+.fi
1483+
1484+You can also explicitly change the name field of a file upload part by setting
1485+filename=, like this:
1486+.nf
1487+
1488+curl \-F "file=@localfile;filename=nameinpost" example.com
1489+.fi
1490+
1491+If filename/path contains \(aq,\(aq or \(aq;\(aq, it must be quoted by double\-quotes like:
1492+.nf
1493+
1494+curl \-F "file=@\\"local,file\\";filename=\\"name;in;post\\"" example.com
1495+.fi
1496+
1497+or
1498+.nf
1499+
1500+curl \-F \(aqfile=@"local,file";filename="name;in;post"\(aq example.com
1501+.fi
1502+
1503+Note that if a filename/path is quoted by double\-quotes, any double\-quote
1504+or backslash within the filename must be escaped by backslash.
1505+
1506+Quoting must also be applied to non\-file data if it contains semicolons,
1507+leading/trailing spaces or leading double quotes:
1508+.nf
1509+
1510+curl \-F \(aqcolors="red; green; blue";type=text/x\-myapp\(aq example.com
1511+.fi
1512+
1513+You can add custom headers to the field by setting headers=, like
1514+.nf
1515+
1516+curl \-F "submit=OK;headers=\\"X\-submit\-type: OK\\"" example.com
1517+.fi
1518+
1519+or
1520+.nf
1521+
1522+curl \-F "submit=OK;headers=@headerfile" example.com
1523+.fi
1524+
1525+The headers= keyword may appear more that once and above notes about quoting
1526+apply. When headers are read from a file, Empty lines and lines starting
1527+with \(aq#\(aq are comments and ignored; each header can be folded by splitting
1528+between two words and starting the continuation line with a space; embedded
1529+carriage\-returns and trailing spaces are stripped.
1530+Here is an example of a header file contents:
1531+.nf
1532+
1533+# This file contain two headers.
1534+X\-header\-1: this is a header
1535+
1536+# The following header is folded.
1537+X\-header\-2: this is
1538+ another header
1539+.fi
1540+
1541+To support sending multipart mail messages, the syntax is extended as follows:
1542+
1543+- name can be omitted: the equal sign is the first character of the argument,
1544+
1545+- if data starts with \(aq(\(aq, this signals to start a new multipart: it can be
1546+followed by a content type specification.
1547+
1548+- a multipart can be terminated with a \(aq=)\(aq argument.
1549+
1550+Example: the following command sends an SMTP mime email consisting in an
1551+inline part in two alternative formats: plain text and HTML. It attaches a
1552+text file:
1553+.nf
1554+
1555+curl \-F \(aq=(;type=multipart/alternative\(aq \\
1556+ \-F \(aq=plain text message\(aq \\
1557+ \-F \(aq= <body>HTML message</body>;type=text/html\(aq \\
1558+ \-F \(aq=)\(aq \-F \(aq=@textfile.txt\(aq ... smtp://example.com
1559+.fi
1560+
1561+Data can be encoded for transfer using encoder=. Available encodings are
1562+\fIbinary\fP and \fI8bit\fP that do nothing else than adding the corresponding
1563+Content\-Transfer\-Encoding header, \fI7bit\fP that only rejects 8\-bit characters
1564+with a transfer error, \fIquoted\-printable\fP and \fIbase64\fP that encodes data
1565+according to the corresponding schemes, limiting lines length to 76
1566+characters.
1567+
1568+Example: send multipart mail with a quoted\-printable text message and a
1569+base64 attached file:
1570+.nf
1571+
1572+curl \-F \(aq=text message;encoder=quoted\-printable\(aq \\
1573+ \-F \(aq=@localfile;encoder=base64\(aq ... smtp://example.com
1574+.fi
1575+
1576+See further examples and details in the MANUAL.
1577+
1578+--form can be used several times in a command line
1579+
1580+Example:
1581+.nf
1582+ curl --form "name=curl" --form "file=@loadthis" https://example.com
1583+.fi
1584+
1585+See also \fI-d, \-\-data\fP, \fI\-\-form\-string\fP and \fI\-\-form\-escape\fP. This option is mutually exclusive to \fI-d, \-\-data\fP and \fI-I, \-\-head\fP and \fI-T, \-\-upload\-file\fP.
1586+.IP "\-\-ftp\-account <data>"
1587+(FTP) When an FTP server asks for "account data" after user name and password has
1588+been provided, this data is sent off using the ACCT command.
1589+
1590+If --ftp-account is provided several times, the last set value is used.
1591+
1592+Example:
1593+.nf
1594+ curl --ftp-account "mr.robot" ftp://example.com/
1595+.fi
1596+
1597+See also \fI-u, \-\-user\fP.
1598+.IP "\-\-ftp\-alternative\-to\-user <command>"
1599+(FTP) If authenticating with the USER and PASS commands fails, send this command.
1600+When connecting to Tumbleweed\(aqs Secure Transport server over FTPS using a
1601+client certificate, using "SITE AUTH" tells the server to retrieve the
1602+username from the certificate.
1603+
1604+If --ftp-alternative-to-user is provided several times, the last set value is used.
1605+
1606+Example:
1607+.nf
1608+ curl --ftp-alternative-to-user "U53r" ftp://example.com
1609+.fi
1610+
1611+See also \fI\-\-ftp\-account\fP and \fI-u, \-\-user\fP.
1612+.IP "\-\-ftp\-create\-dirs"
1613+(FTP SFTP) When an FTP or SFTP URL/operation uses a path that does not currently exist on
1614+the server, the standard behavior of curl is to fail. Using this option, curl
1615+instead attempts to create missing directories.
1616+
1617+Providing --ftp-create-dirs multiple times has no extra effect.
1618+Disable it again with \-\-no-ftp-create-dirs.
1619+
1620+Example:
1621+.nf
1622+ curl --ftp-create-dirs -T file ftp://example.com/remote/path/file
1623+.fi
1624+
1625+See also \fI\-\-create\-dirs\fP.
1626+.IP "\-\-ftp\-method <method>"
1627+(FTP) Control what method curl should use to reach a file on an FTP(S)
1628+server. The method argument should be one of the following alternatives:
1629+.RS
1630+.IP multicwd
1631+curl does a single CWD operation for each path part in the given URL. For deep
1632+hierarchies this means many commands. This is how RFC 1738 says it should
1633+be done. This is the default but the slowest behavior.
1634+.IP nocwd
1635+curl does no CWD at all. curl does SIZE, RETR, STOR etc and give a full
1636+path to the server for all these commands. This is the fastest behavior.
1637+.IP singlecwd
1638+curl does one CWD with the full target directory and then operates on the file
1639+\&"normally" (like in the multicwd case). This is somewhat more standards
1640+compliant than \(aqnocwd\(aq but without the full penalty of \(aqmulticwd\(aq.
1641+.RE
1642+.IP
1643+
1644+If --ftp-method is provided several times, the last set value is used.
1645+
1646+Examples:
1647+.nf
1648+ curl --ftp-method multicwd ftp://example.com/dir1/dir2/file
1649+ curl --ftp-method nocwd ftp://example.com/dir1/dir2/file
1650+ curl --ftp-method singlecwd ftp://example.com/dir1/dir2/file
1651+.fi
1652+
1653+See also \fI-l, \-\-list\-only\fP.
1654+.IP "\-\-ftp\-pasv"
1655+(FTP) Use passive mode for the data connection. Passive is the internal default
1656+behavior, but using this option can be used to override a previous \fI\-P, \-\-ftp\-port\fP
1657+option.
1658+
1659+Reversing an enforced passive really is not doable but you must then instead
1660+enforce the correct \fI\-P, \-\-ftp\-port\fP again.
1661+
1662+Passive mode means that curl tries the EPSV command first and then PASV,
1663+unless \fI\-\-disable\-epsv\fP is used.
1664+
1665+Providing --ftp-pasv multiple times has no extra effect.
1666+Disable it again with \-\-no-ftp-pasv.
1667+
1668+Example:
1669+.nf
1670+ curl --ftp-pasv ftp://example.com/
1671+.fi
1672+
1673+See also \fI\-\-disable\-epsv\fP.
1674+.IP "\-P, \-\-ftp\-port <address>"
1675+(FTP) Reverses the default initiator/listener roles when connecting with FTP. This
1676+option makes curl use active mode. curl then tells the server to connect back
1677+to the client\(aqs specified address and port, while passive mode asks the server
1678+to setup an IP address and port for it to connect to. <address> should be one
1679+of:
1680+.RS
1681+.IP interface
1682+e.g. \fBeth0\fP to specify which interface\(aqs IP address you want to use (Unix only)
1683+.IP "IP address"
1684+e.g. \fB192.168.10.1\fP to specify the exact IP address
1685+.IP "host name"
1686+e.g. \fBmy.host.domain\fP to specify the machine
1687+.IP -
1688+make curl pick the same IP address that is already used for the control
1689+connection. This is the recommended choice.
1690+.RE
1691+.IP
1692+Disable the use of PORT with \fI\-\-ftp\-pasv\fP. Disable the attempt to use the EPRT
1693+command instead of PORT by using \fI\-\-disable\-eprt\fP. EPRT is really PORT++.
1694+
1695+You can also append ":[start]\-[end]" to the right of the address, to tell
1696+curl what TCP port range to use. That means you specify a port range, from a
1697+lower to a higher number. A single number works as well, but do note that it
1698+increases the risk of failure since the port may not be available.
1699+
1700+.RE
1701+.IP
1702+
1703+If --ftp-port is provided several times, the last set value is used.
1704+
1705+Examples:
1706+.nf
1707+ curl -P - ftp:/example.com
1708+ curl -P eth0 ftp:/example.com
1709+ curl -P 192.168.0.2 ftp:/example.com
1710+.fi
1711+
1712+See also \fI\-\-ftp\-pasv\fP and \fI\-\-disable\-eprt\fP.
1713+.IP "\-\-ftp\-pret"
1714+(FTP) Tell curl to send a PRET command before PASV (and EPSV). Certain FTP servers,
1715+mainly drftpd, require this non\-standard command for directory listings as
1716+well as up and downloads in PASV mode.
1717+
1718+Providing --ftp-pret multiple times has no extra effect.
1719+Disable it again with \-\-no-ftp-pret.
1720+
1721+Example:
1722+.nf
1723+ curl --ftp-pret ftp://example.com/
1724+.fi
1725+
1726+See also \fI-P, \-\-ftp\-port\fP and \fI\-\-ftp\-pasv\fP.
1727+.IP "\-\-ftp\-skip\-pasv\-ip"
1728+(FTP) Tell curl to not use the IP address the server suggests in its response to
1729+curl\(aqs PASV command when curl connects the data connection. Instead curl
1730+reuses the same IP address it already uses for the control connection.
1731+
1732+This option is enabled by default (added in 7.74.0).
1733+
1734+This option has no effect if PORT, EPRT or EPSV is used instead of PASV.
1735+
1736+Providing --ftp-skip-pasv-ip multiple times has no extra effect.
1737+Disable it again with \-\-no-ftp-skip-pasv-ip.
1738+
1739+Example:
1740+.nf
1741+ curl --ftp-skip-pasv-ip ftp://example.com/
1742+.fi
1743+
1744+See also \fI\-\-ftp\-pasv\fP.
1745+.IP "\-\-ftp\-ssl\-ccc\-mode <active/passive>"
1746+(FTP) Sets the CCC mode. The passive mode does not initiate the shutdown, but
1747+instead waits for the server to do it, and does not reply to the shutdown from
1748+the server. The active mode initiates the shutdown and waits for a reply from
1749+the server.
1750+
1751+Providing --ftp-ssl-ccc-mode multiple times has no extra effect.
1752+Disable it again with \-\-no-ftp-ssl-ccc-mode.
1753+
1754+Example:
1755+.nf
1756+ curl --ftp-ssl-ccc-mode active --ftp-ssl-ccc ftps://example.com/
1757+.fi
1758+
1759+See also \fI\-\-ftp\-ssl\-ccc\fP.
1760+.IP "\-\-ftp\-ssl\-ccc"
1761+(FTP) Use CCC (Clear Command Channel) Shuts down the SSL/TLS layer after
1762+authenticating. The rest of the control channel communication is be
1763+unencrypted. This allows NAT routers to follow the FTP transaction. The
1764+default mode is passive.
1765+
1766+Providing --ftp-ssl-ccc multiple times has no extra effect.
1767+Disable it again with \-\-no-ftp-ssl-ccc.
1768+
1769+Example:
1770+.nf
1771+ curl --ftp-ssl-ccc ftps://example.com/
1772+.fi
1773+
1774+See also \fI\-\-ssl\fP and \fI\-\-ftp\-ssl\-ccc\-mode\fP.
1775+.IP "\-\-ftp\-ssl\-control"
1776+(FTP) Require SSL/TLS for the FTP login, clear for transfer. Allows secure
1777+authentication, but non\-encrypted data transfers for efficiency. Fails the
1778+transfer if the server does not support SSL/TLS.
1779+
1780+Providing --ftp-ssl-control multiple times has no extra effect.
1781+Disable it again with \-\-no-ftp-ssl-control.
1782+
1783+Example:
1784+.nf
1785+ curl --ftp-ssl-control ftp://example.com
1786+.fi
1787+
1788+See also \fI\-\-ssl\fP.
1789+.IP "\-G, \-\-get"
1790+(HTTP) When used, this option makes all data specified with \fI\-d, \-\-data\fP, \fI\-\-data\-binary\fP
1791+or \fI\-\-data\-urlencode\fP to be used in an HTTP GET request instead of the POST
1792+request that otherwise would be used. The data is appended to the URL
1793+with a \(aq?\(aq separator.
1794+
1795+If used in combination with \fI\-I, \-\-head\fP, the POST data is instead appended to the
1796+URL with a HEAD request.
1797+
1798+Providing --get multiple times has no extra effect.
1799+Disable it again with \-\-no-get.
1800+
1801+Examples:
1802+.nf
1803+ curl --get https://example.com
1804+ curl --get -d "tool=curl" -d "age=old" https://example.com
1805+ curl --get -I -d "tool=curl" https://example.com
1806+.fi
1807+
1808+See also \fI-d, \-\-data\fP and \fI-X, \-\-request\fP.
1809+.IP "\-g, \-\-globoff"
1810+This option switches off the "URL globbing parser". When you set this option,
1811+you can specify URLs that contain the letters {}[] without having curl itself
1812+interpret them. Note that these letters are not normal legal URL contents but
1813+they should be encoded according to the URI standard.
1814+
1815+Providing --globoff multiple times has no extra effect.
1816+Disable it again with \-\-no-globoff.
1817+
1818+Example:
1819+.nf
1820+ curl -g "https://example.com/{[]}}}}"
1821+.fi
1822+
1823+See also \fI-K, \-\-config\fP and \fI-q, \-\-disable\fP.
1824+.IP "\-\-happy\-eyeballs\-timeout\-ms <milliseconds>"
1825+Happy Eyeballs is an algorithm that attempts to connect to both IPv4 and IPv6
1826+addresses for dual\-stack hosts, giving IPv6 a head\-start of the specified
1827+number of milliseconds. If the IPv6 address cannot be connected to within that
1828+time, then a connection attempt is made to the IPv4 address in parallel. The
1829+first connection to be established is the one that is used.
1830+
1831+The range of suggested useful values is limited. Happy Eyeballs RFC 6555 says
1832+\&"It is RECOMMENDED that connection attempts be paced 150\-250 ms apart to
1833+balance human factors against network load." libcurl currently defaults to
1834+200 ms. Firefox and Chrome currently default to 300 ms.
1835+
1836+If --happy-eyeballs-timeout-ms is provided several times, the last set value is used.
1837+
1838+Example:
1839+.nf
1840+ curl --happy-eyeballs-timeout-ms 500 https://example.com
1841+.fi
1842+
1843+See also \fI-m, \-\-max\-time\fP and \fI\-\-connect\-timeout\fP. Added in 7.59.0.
1844+.IP "\-\-haproxy\-clientip <IP address>"
1845+(HTTP) Sets a client IP in HAProxy PROXY protocol v1 header at the beginning of the
1846+connection.
1847+
1848+For valid requests, IPv4 addresses must be indicated as a series of exactly
1849+4 integers in the range [0..255] inclusive written in decimal representation
1850+separated by exactly one dot between each other. Heading zeroes are not
1851+permitted in front of numbers in order to avoid any possible confusion
1852+with octal numbers. IPv6 addresses must be indicated as series of 4 hexadecimal
1853+digits (upper or lower case) delimited by colons between each other, with the
1854+acceptance of one double colon sequence to replace the largest acceptable range
1855+of consecutive zeroes. The total number of decoded bits must exactly be 128.
1856+
1857+Otherwise, any string can be accepted for the client IP and get sent.
1858+
1859+It replaces \fI\-\-haproxy\-protocol\fP if used, it is not necessary to specify both flags.
1860+
1861+If --haproxy-clientip is provided several times, the last set value is used.
1862+
1863+Example:
1864+.nf
1865+ curl --haproxy-clientip $IP
1866+.fi
1867+
1868+See also \fI-x, \-\-proxy\fP. Added in 8.2.0.
1869+.IP "\-\-haproxy\-protocol"
1870+(HTTP) Send a HAProxy PROXY protocol v1 header at the beginning of the
1871+connection. This is used by some load balancers and reverse proxies to
1872+indicate the client\(aqs true IP address and port.
1873+
1874+This option is primarily useful when sending test requests to a service that
1875+expects this header.
1876+
1877+Providing --haproxy-protocol multiple times has no extra effect.
1878+Disable it again with \-\-no-haproxy-protocol.
1879+
1880+Example:
1881+.nf
1882+ curl --haproxy-protocol https://example.com
1883+.fi
1884+
1885+See also \fI-x, \-\-proxy\fP. Added in 7.60.0.
1886+.IP "\-I, \-\-head"
1887+(HTTP FTP FILE) Fetch the headers only! HTTP\-servers feature the command HEAD which this uses
1888+to get nothing but the header of a document. When used on an FTP or FILE file,
1889+curl displays the file size and last modification time only.
1890+
1891+Providing --head multiple times has no extra effect.
1892+Disable it again with \-\-no-head.
1893+
1894+Example:
1895+.nf
1896+ curl -I https://example.com
1897+.fi
1898+
1899+See also \fI-G, \-\-get\fP, \fI-v, \-\-verbose\fP and \fI\-\-trace\-ascii\fP.
1900+.IP "\-H, \-\-header <header/@file>"
1901+(HTTP IMAP SMTP) Extra header to include in information sent. When used within an HTTP request,
1902+it is added to the regular request headers.
1903+
1904+For an IMAP or SMTP MIME uploaded mail built with \fI\-F, \-\-form\fP options, it is
1905+prepended to the resulting MIME document, effectively including it at the mail
1906+global level. It does not affect raw uploaded mails (Added in 7.56.0).
1907+
1908+You may specify any number of extra headers. Note that if you should add a
1909+custom header that has the same name as one of the internal ones curl would
1910+use, your externally set header is used instead of the internal one. This
1911+allows you to make even trickier stuff than curl would normally do. You should
1912+not replace internally set headers without knowing perfectly well what you are
1913+doing. Remove an internal header by giving a replacement without content on
1914+the right side of the colon, as in: \-H "Host:". If you send the custom header
1915+with no\-value then its header must be terminated with a semicolon, such as \\-H
1916+\&"X\-Custom\-Header;" to send "X\-Custom\-Header:".
1917+
1918+curl makes sure that each header you add/replace is sent with the proper
1919+end\-of\-line marker, you should thus \fBnot\fP add that as a part of the header
1920+content: do not add newlines or carriage returns, they only mess things up for
1921+you. curl passes on the verbatim string you give it without any filter or
1922+other safe guards. That includes white space and control characters.
1923+
1924+This option can take an argument in @filename style, which then adds a header
1925+for each line in the input file. Using @\- makes curl read the header file from
1926+stdin. Added in 7.55.0.
1927+
1928+Please note that most anti\-spam utilities check the presence and value of
1929+several MIME mail headers: these are "From:", "To:", "Date:" and "Subject:"
1930+among others and should be added with this option.
1931+
1932+You need \fI\-\-proxy\-header\fP to send custom headers intended for an HTTP
1933+proxy. Added in 7.37.0.
1934+
1935+Passing on a "Transfer\-Encoding: chunked" header when doing an HTTP request
1936+with a request body, makes curl send the data using chunked encoding.
1937+
1938+\fBWARNING\fP: headers set with this option are set in all HTTP requests \- even
1939+after redirects are followed, like when told with \fI\-L, \-\-location\fP. This can lead to
1940+the header being sent to other hosts than the original host, so sensitive
1941+headers should be used with caution combined with following redirects.
1942+
1943+--header can be used several times in a command line
1944+
1945+Examples:
1946+.nf
1947+ curl -H "X-First-Name: Joe" https://example.com
1948+ curl -H "User-Agent: yes-please/2000" https://example.com
1949+ curl -H "Host:" https://example.com
1950+ curl -H @headers.txt https://example.com
1951+.fi
1952+
1953+See also \fI-A, \-\-user\-agent\fP and \fI-e, \-\-referer\fP.
1954+.IP "\-h, \-\-help <category>"
1955+Usage help. This lists all curl command line options within the given
1956+\fBcategory\fP.
1957+
1958+If no argument is provided, curl displays only the most important command line
1959+arguments.
1960+
1961+For category \fBall\fP, curl displays help for all options.
1962+
1963+If \fBcategory\fP is specified, curl displays all available help categories.
1964+
1965+Example:
1966+.nf
1967+ curl --help all
1968+.fi
1969+
1970+See also \fI-v, \-\-verbose\fP.
1971+.IP "\-\-hostpubmd5 <md5>"
1972+(SFTP SCP) Pass a string containing 32 hexadecimal digits. The string should be the 128
1973+bit \fBMD5\fP checksum of the remote host\(aqs public key, curl refuses the
1974+connection with the host unless the checksums match.
1975+
1976+If --hostpubmd5 is provided several times, the last set value is used.
1977+
1978+Example:
1979+.nf
1980+ curl --hostpubmd5 e5c1c49020640a5ab0f2034854c321a8 sftp://example.com/
1981+.fi
1982+
1983+See also \fI\-\-hostpubsha256\fP.
1984+.IP "\-\-hostpubsha256 <sha256>"
1985+(SFTP SCP) Pass a string containing a Base64\-encoded SHA256 hash of the remote host\(aqs
1986+public key. Curl refuses the connection with the host unless the hashes match.
1987+
1988+This feature requires libcurl to be built with libssh2 and does not work with
1989+other SSH backends.
1990+
1991+If --hostpubsha256 is provided several times, the last set value is used.
1992+
1993+Example:
1994+.nf
1995+ curl --hostpubsha256 NDVkMTQxMGQ1ODdmMjQ3MjczYjAyOTY5MmRkMjVmNDQ= sftp://example.com/
1996+.fi
1997+
1998+See also \fI\-\-hostpubmd5\fP. Added in 7.80.0.
1999+.IP "\-\-hsts <file name>"
2000+(HTTPS) This option enables HSTS for the transfer. If the file name points to an
2001+existing HSTS cache file, that is used. After a completed transfer, the
2002+cache is saved to the file name again if it has been modified.
2003+
2004+If curl is told to use HTTP:// for a transfer involving a host name that
2005+exists in the HSTS cache, it upgrades the transfer to use HTTPS. Each HSTS
2006+cache entry has an individual life time after which the upgrade is no longer
2007+performed.
2008+
2009+Specify a "" file name (zero length) to avoid loading/saving and make curl
2010+just handle HSTS in memory.
2011+
2012+If this option is used several times, curl loads contents from all the
2013+files but the last one is used for saving.
2014+
2015+--hsts can be used several times in a command line
2016+
2017+Example:
2018+.nf
2019+ curl --hsts cache.txt https://example.com
2020+.fi
2021+
2022+See also \fI\-\-proto\fP. Added in 7.74.0.
2023+.IP "\-\-http0.9"
2024+(HTTP) Tells curl to be fine with HTTP version 0.9 response.
2025+
2026+HTTP/0.9 is a response without headers and therefore you can also connect with
2027+this to non\-HTTP servers and still get a response since curl simply
2028+transparently downgrades \- if allowed.
2029+
2030+HTTP/0.9 is disabled by default (added in 7.66.0)
2031+
2032+Providing --http0.9 multiple times has no extra effect.
2033+Disable it again with \-\-no-http0.9.
2034+
2035+Example:
2036+.nf
2037+ curl --http0.9 https://example.com
2038+.fi
2039+
2040+See also \fI\-\-http1.1\fP, \fI\-\-http2\fP and \fI\-\-http3\fP. Added in 7.64.0.
2041+.IP "\-0, \-\-http1.0"
2042+(HTTP) Tells curl to use HTTP version 1.0 instead of using its internally preferred
2043+HTTP version.
2044+
2045+Providing --http1.0 multiple times has no extra effect.
2046+
2047+Example:
2048+.nf
2049+ curl --http1.0 https://example.com
2050+.fi
2051+
2052+See also \fI\-\-http0.9\fP and \fI\-\-http1.1\fP. This option is mutually exclusive to \fI\-\-http1.1\fP and \fI\-\-http2\fP and \fI\-\-http2\-prior\-knowledge\fP and \fI\-\-http3\fP.
2053+.IP "\-\-http1.1"
2054+(HTTP) Tells curl to use HTTP version 1.1.
2055+
2056+Providing --http1.1 multiple times has no extra effect.
2057+
2058+Example:
2059+.nf
2060+ curl --http1.1 https://example.com
2061+.fi
2062+
2063+See also \fI-0, \-\-http1.0\fP and \fI\-\-http0.9\fP. This option is mutually exclusive to \fI-0, \-\-http1.0\fP and \fI\-\-http2\fP and \fI\-\-http2\-prior\-knowledge\fP and \fI\-\-http3\fP.
2064+.IP "\-\-http2\-prior\-knowledge"
2065+(HTTP) Tells curl to issue its non\-TLS HTTP requests using HTTP/2 without HTTP/1.1
2066+Upgrade. It requires prior knowledge that the server supports HTTP/2 straight
2067+away. HTTPS requests still do HTTP/2 the standard way with negotiated protocol
2068+version in the TLS handshake.
2069+
2070+Providing --http2-prior-knowledge multiple times has no extra effect.
2071+Disable it again with \-\-no-http2-prior-knowledge.
2072+
2073+Example:
2074+.nf
2075+ curl --http2-prior-knowledge https://example.com
2076+.fi
2077+
2078+See also \fI\-\-http2\fP and \fI\-\-http3\fP. \fI\-\-http2\-prior\-knowledge\fP requires that the underlying libcurl was built to support HTTP/2. This option is mutually exclusive to \fI\-\-http1.1\fP and \fI-0, \-\-http1.0\fP and \fI\-\-http2\fP and \fI\-\-http3\fP.
2079+.IP "\-\-http2"
2080+(HTTP) Tells curl to use HTTP version 2.
2081+
2082+For HTTPS, this means curl negotiates HTTP/2 in the TLS handshake. curl does
2083+this by default.
2084+
2085+For HTTP, this means curl attempts to upgrade the request to HTTP/2 using the
2086+Upgrade: request header.
2087+
2088+When curl uses HTTP/2 over HTTPS, it does not itself insist on TLS 1.2 or
2089+higher even though that is required by the specification. A user can add this
2090+version requirement with \fI\-\-tlsv1.2\fP.
2091+
2092+Providing --http2 multiple times has no extra effect.
2093+
2094+Example:
2095+.nf
2096+ curl --http2 https://example.com
2097+.fi
2098+
2099+See also \fI\-\-http1.1\fP, \fI\-\-http3\fP and \fI\-\-no\-alpn\fP. \fI\-\-http2\fP requires that the underlying libcurl was built to support HTTP/2. This option is mutually exclusive to \fI\-\-http1.1\fP and \fI-0, \-\-http1.0\fP and \fI\-\-http2\-prior\-knowledge\fP and \fI\-\-http3\fP.
2100+.IP "\-\-http3\-only"
2101+(HTTP) Instructs curl to use HTTP/3 to the host in the URL, with no fallback to
2102+earlier HTTP versions. HTTP/3 can only be used for HTTPS and not for HTTP
2103+URLs. For HTTP, this option triggers an error.
2104+
2105+This option allows a user to avoid using the Alt\-Svc method of upgrading to
2106+HTTP/3 when you know that the target speaks HTTP/3 on the given host and port.
2107+
2108+This option makes curl fail if a QUIC connection cannot be established, it
2109+does not attempt any other HTTP versions on its own. Use \fI\-\-http3\fP for similar
2110+functionality \fIwith\fP a fallback.
2111+
2112+Providing --http3-only multiple times has no extra effect.
2113+
2114+Example:
2115+.nf
2116+ curl --http3-only https://example.com
2117+.fi
2118+
2119+See also \fI\-\-http1.1\fP, \fI\-\-http2\fP and \fI\-\-http3\fP. \fI\-\-http3\-only\fP requires that the underlying libcurl was built to support HTTP/3. This option is mutually exclusive to \fI\-\-http1.1\fP and \fI-0, \-\-http1.0\fP and \fI\-\-http2\fP and \fI\-\-http2\-prior\-knowledge\fP and \fI\-\-http3\fP. Added in 7.88.0.
2120+.IP "\-\-http3"
2121+(HTTP) Tells curl to try HTTP/3 to the host in the URL, but fallback to earlier
2122+HTTP versions if the HTTP/3 connection establishment fails. HTTP/3 is only
2123+available for HTTPS and not for HTTP URLs.
2124+
2125+This option allows a user to avoid using the Alt\-Svc method of upgrading to
2126+HTTP/3 when you know that the target speaks HTTP/3 on the given host and port.
2127+
2128+When asked to use HTTP/3, curl issues a separate attempt to use older HTTP
2129+versions with a slight delay, so if the HTTP/3 transfer fails or is slow, curl
2130+still tries to proceed with an older HTTP version.
2131+
2132+Use \fI\-\-http3\-only\fP for similar functionality \fIwithout\fP a fallback.
2133+
2134+Providing --http3 multiple times has no extra effect.
2135+
2136+Example:
2137+.nf
2138+ curl --http3 https://example.com
2139+.fi
2140+
2141+See also \fI\-\-http1.1\fP and \fI\-\-http2\fP. \fI\-\-http3\fP requires that the underlying libcurl was built to support HTTP/3. This option is mutually exclusive to \fI\-\-http1.1\fP and \fI-0, \-\-http1.0\fP and \fI\-\-http2\fP and \fI\-\-http2\-prior\-knowledge\fP and \fI\-\-http3\-only\fP. Added in 7.66.0.
2142+.IP "\-\-ignore\-content\-length"
2143+(FTP HTTP) For HTTP, Ignore the Content\-Length header. This is particularly useful for
2144+servers running Apache 1.x, which reports incorrect Content\-Length for
2145+files larger than 2 gigabytes.
2146+
2147+For FTP, this makes curl skip the SIZE command to figure out the size before
2148+downloading a file.
2149+
2150+This option does not work for HTTP if libcurl was built to use hyper.
2151+
2152+Providing --ignore-content-length multiple times has no extra effect.
2153+Disable it again with \-\-no-ignore-content-length.
2154+
2155+Example:
2156+.nf
2157+ curl --ignore-content-length https://example.com
2158+.fi
2159+
2160+See also \fI\-\-ftp\-skip\-pasv\-ip\fP.
2161+.IP "\-i, \-\-include"
2162+(HTTP FTP) Include response headers in the output. HTTP response headers can include
2163+things like server name, cookies, date of the document, HTTP version and
2164+more... With non\-HTTP protocols, the "headers" are other server communication.
2165+
2166+To view the request headers, consider the \fI\-v, \-\-verbose\fP option.
2167+
2168+Prior to 7.75.0 curl did not print the headers if \fI\-f, \-\-fail\fP was used in
2169+combination with this option and there was error reported by server.
2170+
2171+Providing --include multiple times has no extra effect.
2172+Disable it again with \-\-no-include.
2173+
2174+Example:
2175+.nf
2176+ curl -i https://example.com
2177+.fi
2178+
2179+See also \fI-v, \-\-verbose\fP.
2180+.IP "\-k, \-\-insecure"
2181+(TLS SFTP SCP) By default, every secure connection curl makes is verified to be secure before
2182+the transfer takes place. This option makes curl skip the verification step
2183+and proceed without checking.
2184+
2185+When this option is not used for protocols using TLS, curl verifies the
2186+server\(aqs TLS certificate before it continues: that the certificate contains
2187+the right name which matches the host name used in the URL and that the
2188+certificate has been signed by a CA certificate present in the cert store.
2189+See this online resource for further details:
2190+\fBhttps://curl.se/docs/sslcerts.html\fP
2191+
2192+For SFTP and SCP, this option makes curl skip the \fIknown_hosts\fP verification.
2193+\fIknown_hosts\fP is a file normally stored in the user\(aqs home directory in the
2194+\&".ssh" subdirectory, which contains host names and their public keys.
2195+
2196+\fBWARNING\fP: using this option makes the transfer insecure.
2197+
2198+When curl uses secure protocols it trusts responses and allows for example
2199+HSTS and Alt\-Svc information to be stored and used subsequently. Using
2200+\fI\-k, \-\-insecure\fP can make curl trust and use such information from malicious
2201+servers.
2202+
2203+Providing --insecure multiple times has no extra effect.
2204+Disable it again with \-\-no-insecure.
2205+
2206+Example:
2207+.nf
2208+ curl --insecure https://example.com
2209+.fi
2210+
2211+See also \fI\-\-proxy\-insecure\fP, \fI\-\-cacert\fP and \fI\-\-capath\fP.
2212+.IP "\-\-interface <name>"
2213+Perform an operation using a specified interface. You can enter interface
2214+name, IP address or host name. An example could look like:
2215+.nf
2216+
2217+curl \--interface eth0:1 https://www.example.com/
2218+.fi
2219+
2220+On Linux it can be used to specify a \fBVRF\fP, but the binary needs to either
2221+have \fBCAP_NET_RAW\fP or to be run as root. More information about Linux
2222+\fBVRF\fP: https://www.kernel.org/doc/Documentation/networking/vrf.txt
2223+
2224+If --interface is provided several times, the last set value is used.
2225+
2226+Example:
2227+.nf
2228+ curl --interface eth0 https://example.com
2229+.fi
2230+
2231+See also \fI\-\-dns\-interface\fP.
2232+.IP "\-\-ipfs\-gateway <URL>"
2233+(IPFS) Specify which gateway to use for IPFS and IPNS URLs. Not specifying this will
2234+instead make curl check if the IPFS_GATEWAY environment variable is set, or if
2235+a "~/.ipfs/gateway" file holding the gateway URL exists.
2236+
2237+If you run a local IPFS node, this gateway is by default available under
2238+\&"http://localhost:8080". A full example URL would look like:
2239+.nf
2240+
2241+curl \--ipfs\-gateway http://localhost:8080 ipfs://bafybeigagd5nmnn2iys2f3doro7ydrevyr2mzarwidgadawmamiteydbzi
2242+.fi
2243+
2244+There are many public IPFS gateways. See for example:
2245+https://ipfs.github.io/public\-gateway\-checker/
2246+
2247+WARNING: If you opt to go for a remote gateway you should be aware that you
2248+completely trust the gateway. This is fine in local gateways as you host it
2249+yourself. With remote gateways there could potentially be a malicious actor
2250+returning you data that does not match the request you made, inspect or even
2251+interfere with the request. You will not notice this when using curl. A
2252+mitigation could be to go for a "trustless" gateway. This means you locally
2253+verify that the data. Consult the docs page on trusted vs trustless:
2254+https://docs.ipfs.tech/reference/http/gateway/#trusted\-vs\-trustless
2255+
2256+If --ipfs-gateway is provided several times, the last set value is used.
2257+
2258+Example:
2259+.nf
2260+ curl --ipfs-gateway https://example.com ipfs://
2261+.fi
2262+
2263+See also \fI-h, \-\-help\fP and \fI-M, \-\-manual\fP. Added in 8.4.0.
2264+.IP "\-4, \-\-ipv4"
2265+This option tells curl to use IPv4 addresses only when resolving host names,
2266+and not for example try IPv6.
2267+
2268+Providing --ipv4 multiple times has no extra effect.
2269+
2270+Example:
2271+.nf
2272+ curl --ipv4 https://example.com
2273+.fi
2274+
2275+See also \fI\-\-http1.1\fP and \fI\-\-http2\fP. This option is mutually exclusive to \fI-6, \-\-ipv6\fP.
2276+.IP "\-6, \-\-ipv6"
2277+This option tells curl to use IPv6 addresses only when resolving host names,
2278+and not for example try IPv4.
2279+
2280+Providing --ipv6 multiple times has no extra effect.
2281+
2282+Example:
2283+.nf
2284+ curl --ipv6 https://example.com
2285+.fi
2286+
2287+See also \fI\-\-http1.1\fP and \fI\-\-http2\fP. This option is mutually exclusive to \fI-4, \-\-ipv4\fP.
2288+.IP "\-\-json <data>"
2289+(HTTP) Sends the specified JSON data in a POST request to the HTTP server. \fI\-\-json\fP
2290+works as a shortcut for passing on these three options:
2291+.nf
2292+
2293+-\-data [arg]
2294+-\-header "Content\-Type: application/json"
2295+-\-header "Accept: application/json"
2296+.fi
2297+
2298+There is \fBno verification\fP that the passed in data is actual JSON or that
2299+the syntax is correct.
2300+
2301+If you start the data with the letter @, the rest should be a file name to
2302+read the data from, or a single dash (\-) if you want curl to read the data
2303+from stdin. Posting data from a file named \(aqfoobar\(aq would thus be done with
2304+\fI\-\-json\fP @foobar and to instead read the data from stdin, use \fI\-\-json\fP @\-.
2305+
2306+If this option is used more than once on the same command line, the additional
2307+data pieces are concatenated to the previous before sending.
2308+
2309+The headers this option sets can be overridden with \fI\-H, \-\-header\fP as usual.
2310+
2311+--json can be used several times in a command line
2312+
2313+Examples:
2314+.nf
2315+ curl --json '{ "drink": "coffe" }' https://example.com
2316+ curl --json '{ "drink":' --json ' "coffe" }' https://example.com
2317+ curl --json @prepared https://example.com
2318+ curl --json @- https://example.com < json.txt
2319+.fi
2320+
2321+See also \fI\-\-data\-binary\fP and \fI\-\-data\-raw\fP. This option is mutually exclusive to \fI-F, \-\-form\fP and \fI-I, \-\-head\fP and \fI-T, \-\-upload\-file\fP. Added in 7.82.0.
2322+.IP "\-j, \-\-junk\-session\-cookies"
2323+(HTTP) When curl is told to read cookies from a given file, this option makes it
2324+discard all "session cookies". This has the same effect as if a new session is
2325+started. Typical browsers discard session cookies when they are closed down.
2326+
2327+Providing --junk-session-cookies multiple times has no extra effect.
2328+Disable it again with \-\-no-junk-session-cookies.
2329+
2330+Example:
2331+.nf
2332+ curl --junk-session-cookies -b cookies.txt https://example.com
2333+.fi
2334+
2335+See also \fI-b, \-\-cookie\fP and \fI-c, \-\-cookie\-jar\fP.
2336+.IP "\-\-keepalive\-time <seconds>"
2337+This option sets the time a connection needs to remain idle before sending
2338+keepalive probes and the time between individual keepalive probes. It is
2339+currently effective on operating systems offering the "TCP_KEEPIDLE" and
2340+\&"TCP_KEEPINTVL" socket options (meaning Linux, recent AIX, HP\-UX and more).
2341+Keepalive is used by the TCP stack to detect broken networks on idle
2342+connections. The number of missed keepalive probes before declaring the
2343+connection down is OS dependent and is commonly 9 or 10. This option has no
2344+effect if \fI\-\-no\-keepalive\fP is used.
2345+
2346+If unspecified, the option defaults to 60 seconds.
2347+
2348+If --keepalive-time is provided several times, the last set value is used.
2349+
2350+Example:
2351+.nf
2352+ curl --keepalive-time 20 https://example.com
2353+.fi
2354+
2355+See also \fI\-\-no\-keepalive\fP and \fI-m, \-\-max\-time\fP.
2356+.IP "\-\-key\-type <type>"
2357+(TLS) Private key file type. Specify which type your \fI\-\-key\fP provided private key
2358+is. DER, PEM, and ENG are supported. If not specified, PEM is assumed.
2359+
2360+If --key-type is provided several times, the last set value is used.
2361+
2362+Example:
2363+.nf
2364+ curl --key-type DER --key here https://example.com
2365+.fi
2366+
2367+See also \fI\-\-key\fP.
2368+.IP "\-\-key <key>"
2369+(TLS SSH) Private key file name. Allows you to provide your private key in this separate
2370+file. For SSH, if not specified, curl tries the following candidates in order:
2371+\&"~/.ssh/id_rsa", "~/.ssh/id_dsa", "./id_rsa", "./id_dsa".
2372+
2373+If curl is built against OpenSSL library, and the engine pkcs11 is available,
2374+then a PKCS#11 URI (RFC 7512) can be used to specify a private key located in
2375+a PKCS#11 device. A string beginning with "pkcs11:" is interpreted as a
2376+PKCS#11 URI. If a PKCS#11 URI is provided, then the \fI\-\-engine\fP option is set as
2377+\&"pkcs11" if none was provided and the \fI\-\-key\-type\fP option is set as "ENG" if
2378+none was provided.
2379+
2380+If curl is built against Secure Transport or Schannel then this option is
2381+ignored for TLS protocols (HTTPS, etc). Those backends expect the private key
2382+to be already present in the keychain or PKCS#12 file containing the
2383+certificate.
2384+
2385+If --key is provided several times, the last set value is used.
2386+
2387+Example:
2388+.nf
2389+ curl --cert certificate --key here https://example.com
2390+.fi
2391+
2392+See also \fI\-\-key\-type\fP and \fI-E, \-\-cert\fP.
2393+.IP "\-\-krb <level>"
2394+(FTP) Enable Kerberos authentication and use. The level must be entered and should
2395+be one of \(aqclear\(aq, \(aqsafe\(aq, \(aqconfidential\(aq, or \(aqprivate\(aq. Should you use a
2396+level that is not one of these, \(aqprivate\(aq is used.
2397+
2398+If --krb is provided several times, the last set value is used.
2399+
2400+Example:
2401+.nf
2402+ curl --krb clear ftp://example.com/
2403+.fi
2404+
2405+See also \fI\-\-delegation\fP and \fI\-\-ssl\fP. \fI\-\-krb\fP requires that the underlying libcurl was built to support Kerberos.
2406+.IP "\-\-libcurl <file>"
2407+Append this option to any ordinary curl command line, and you get
2408+libcurl\-using C source code written to the file that does the equivalent of
2409+what your command\-line operation does!
2410+
2411+This option is global and does not need to be specified for each use of --next.
2412+
2413+If --libcurl is provided several times, the last set value is used.
2414+
2415+Example:
2416+.nf
2417+ curl --libcurl client.c https://example.com
2418+.fi
2419+
2420+See also \fI-v, \-\-verbose\fP.
2421+.IP "\-\-limit\-rate <speed>"
2422+Specify the maximum transfer rate you want curl to use \- for both downloads
2423+and uploads. This feature is useful if you have a limited pipe and you would like
2424+your transfer not to use your entire bandwidth. To make it slower than it
2425+otherwise would be.
2426+
2427+The given speed is measured in bytes/second, unless a suffix is appended.
2428+Appending \(aqk\(aq or \(aqK\(aq counts the number as kilobytes, \(aqm\(aq or \(aqM\(aq makes it
2429+megabytes, while \(aqg\(aq or \(aqG\(aq makes it gigabytes. The suffixes (k, M, G, T, P)
2430+are 1024 based. For example 1k is 1024. Examples: 200K, 3m and 1G.
2431+
2432+The rate limiting logic works on averaging the transfer speed to no more than
2433+the set threshold over a period of multiple seconds.
2434+
2435+If you also use the \fI\-Y, \-\-speed\-limit\fP option, that option takes precedence and
2436+might cripple the rate\-limiting slightly, to help keeping the speed\-limit
2437+logic working.
2438+
2439+If --limit-rate is provided several times, the last set value is used.
2440+
2441+Examples:
2442+.nf
2443+ curl --limit-rate 100K https://example.com
2444+ curl --limit-rate 1000 https://example.com
2445+ curl --limit-rate 10M https://example.com
2446+.fi
2447+
2448+See also \fI\-\-rate\fP, \fI-Y, \-\-speed\-limit\fP and \fI-y, \-\-speed\-time\fP.
2449+.IP "\-l, \-\-list\-only"
2450+(FTP POP3 SFTP) (FTP)
2451+When listing an FTP directory, this switch forces a name\-only view. This is
2452+especially useful if the user wants to machine\-parse the contents of an FTP
2453+directory since the normal directory view does not use a standard look or
2454+format. When used like this, the option causes an NLST command to be sent to
2455+the server instead of LIST.
2456+
2457+Note: Some FTP servers list only files in their response to NLST; they do not
2458+include sub\-directories and symbolic links.
2459+
2460+(SFTP)
2461+When listing an SFTP directory, this switch forces a name\-only view, one per line.
2462+This is especially useful if the user wants to machine\-parse the contents of an
2463+SFTP directory since the normal directory view provides more information than just
2464+file names.
2465+
2466+(POP3)
2467+When retrieving a specific email from POP3, this switch forces a LIST command
2468+to be performed instead of RETR. This is particularly useful if the user wants
2469+to see if a specific message\-id exists on the server and what size it is.
2470+
2471+Note: When combined with \fI\-X, \-\-request\fP, this option can be used to send a UIDL
2472+command instead, so the user may use the email\(aqs unique identifier rather than
2473+its message\-id to make the request.
2474+
2475+Providing --list-only multiple times has no extra effect.
2476+Disable it again with \-\-no-list-only.
2477+
2478+Example:
2479+.nf
2480+ curl --list-only ftp://example.com/dir/
2481+.fi
2482+
2483+See also \fI-Q, \-\-quote\fP and \fI-X, \-\-request\fP.
2484+.IP "\-\-local\-port <num/range>"
2485+Set a preferred single number or range (FROM\-TO) of local port numbers to use
2486+for the connection(s). Note that port numbers by nature are a scarce resource
2487+so setting this range to something too narrow might cause unnecessary
2488+connection setup failures.
2489+
2490+If --local-port is provided several times, the last set value is used.
2491+
2492+Example:
2493+.nf
2494+ curl --local-port 1000-3000 https://example.com
2495+.fi
2496+
2497+See also \fI-g, \-\-globoff\fP.
2498+.IP "\-\-location\-trusted"
2499+(HTTP) Like \fI\-L, \-\-location\fP, but allows sending the name + password to all hosts that the
2500+site may redirect to. This may or may not introduce a security breach if the
2501+site redirects you to a site to which you send your authentication info
2502+(which is clear\-text in the case of HTTP Basic authentication).
2503+
2504+Providing --location-trusted multiple times has no extra effect.
2505+Disable it again with \-\-no-location-trusted.
2506+
2507+Example:
2508+.nf
2509+ curl --location-trusted -u user:password https://example.com
2510+.fi
2511+
2512+See also \fI-u, \-\-user\fP.
2513+.IP "\-L, \-\-location"
2514+(HTTP) If the server reports that the requested page has moved to a different
2515+location (indicated with a Location: header and a 3XX response code), this
2516+option makes curl redo the request on the new place. If used together with
2517+\fI\-i, \-\-include\fP or \fI\-I, \-\-head\fP, headers from all requested pages are shown.
2518+
2519+When authentication is used, curl only sends its credentials to the initial
2520+host. If a redirect takes curl to a different host, it does not get the
2521+user+password pass on. See also \fI\-\-location\-trusted\fP on how to change this.
2522+
2523+Limit the amount of redirects to follow by using the \fI\-\-max\-redirs\fP option.
2524+
2525+When curl follows a redirect and if the request is a POST, it sends the
2526+following request with a GET if the HTTP response was 301, 302, or 303. If the
2527+response code was any other 3xx code, curl resends the following request using
2528+the same unmodified method.
2529+
2530+You can tell curl to not change POST requests to GET after a 30x response by
2531+using the dedicated options for that: \fI\-\-post301\fP, \fI\-\-post302\fP and \fI\-\-post303\fP.
2532+
2533+The method set with \fI\-X, \-\-request\fP overrides the method curl would otherwise select
2534+to use.
2535+
2536+Providing --location multiple times has no extra effect.
2537+Disable it again with \-\-no-location.
2538+
2539+Example:
2540+.nf
2541+ curl -L https://example.com
2542+.fi
2543+
2544+See also \fI\-\-resolve\fP and \fI\-\-alt\-svc\fP.
2545+.IP "\-\-login\-options <options>"
2546+(IMAP LDAP POP3 SMTP) Specify the login options to use during server authentication.
2547+
2548+You can use login options to specify protocol specific options that may be
2549+used during authentication. At present only IMAP, POP3 and SMTP support login
2550+options. For more information about login options please see RFC 2384,
2551+RFC 5092 and the IETF draft
2552+https://datatracker.ietf.org/doc/html/draft\-earhart\-url\-smtp\-00
2553+
2554+Since 8.2.0, IMAP supports the login option "AUTH=+LOGIN". With this option,
2555+curl uses the plain (not SASL) "LOGIN IMAP" command even if the server
2556+advertises SASL authentication. Care should be taken in using this option, as
2557+it sends your password over the network in plain text. This does not work if
2558+the IMAP server disables the plain "LOGIN" (e.g. to prevent password
2559+snooping).
2560+
2561+If --login-options is provided several times, the last set value is used.
2562+
2563+Example:
2564+.nf
2565+ curl --login-options 'AUTH=*' imap://example.com
2566+.fi
2567+
2568+See also \fI-u, \-\-user\fP.
2569+.IP "\-\-mail\-auth <address>"
2570+(SMTP) Specify a single address. This is used to specify the authentication address
2571+(identity) of a submitted message that is being relayed to another server.
2572+
2573+If --mail-auth is provided several times, the last set value is used.
2574+
2575+Example:
2576+.nf
2577+ curl --mail-auth user@example.come -T mail smtp://example.com/
2578+.fi
2579+
2580+See also \fI\-\-mail\-rcpt\fP and \fI\-\-mail\-from\fP.
2581+.IP "\-\-mail\-from <address>"
2582+(SMTP) Specify a single address that the given mail should get sent from.
2583+
2584+If --mail-from is provided several times, the last set value is used.
2585+
2586+Example:
2587+.nf
2588+ curl --mail-from user@example.com -T mail smtp://example.com/
2589+.fi
2590+
2591+See also \fI\-\-mail\-rcpt\fP and \fI\-\-mail\-auth\fP.
2592+.IP "\-\-mail\-rcpt\-allowfails"
2593+(SMTP) When sending data to multiple recipients, by default curl aborts SMTP
2594+conversation if at least one of the recipients causes RCPT TO command to
2595+return an error.
2596+
2597+The default behavior can be changed by passing \fI\-\-mail\-rcpt\-allowfails\fP
2598+command\-line option which makes curl ignore errors and proceed with the
2599+remaining valid recipients.
2600+
2601+If all recipients trigger RCPT TO failures and this flag is specified, curl
2602+still aborts the SMTP conversation and returns the error received from to the
2603+last RCPT TO command.
2604+
2605+Providing --mail-rcpt-allowfails multiple times has no extra effect.
2606+Disable it again with \-\-no-mail-rcpt-allowfails.
2607+
2608+Example:
2609+.nf
2610+ curl --mail-rcpt-allowfails --mail-rcpt dest@example.com smtp://example.com
2611+.fi
2612+
2613+See also \fI\-\-mail\-rcpt\fP. Added in 7.69.0.
2614+.IP "\-\-mail\-rcpt <address>"
2615+(SMTP) Specify a single email address, user name or mailing list name. Repeat this
2616+option several times to send to multiple recipients.
2617+
2618+When performing an address verification (\fBVRFY\fP command), the recipient should be
2619+specified as the user name or user name and domain (as per Section 3.5 of
2620+RFC 5321).
2621+
2622+When performing a mailing list expand (EXPN command), the recipient should be
2623+specified using the mailing list name, such as "Friends" or "London\-Office".
2624+
2625+
2626+--mail-rcpt can be used several times in a command line
2627+
2628+Example:
2629+.nf
2630+ curl --mail-rcpt user@example.net smtp://example.com
2631+.fi
2632+
2633+See also \fI\-\-mail\-rcpt\-allowfails\fP.
2634+.IP "\-M, \-\-manual"
2635+Manual. Display the huge help text.
2636+
2637+Example:
2638+.nf
2639+ curl --manual
2640+.fi
2641+
2642+See also \fI-v, \-\-verbose\fP, \fI\-\-libcurl\fP and \fI\-\-trace\fP.
2643+.IP "\-\-max\-filesize <bytes>"
2644+(FTP HTTP MQTT) Specify the maximum size (in bytes) of a file to download. If the file
2645+requested is larger than this value, the transfer does not start and curl
2646+returns with exit code 63.
2647+
2648+A size modifier may be used. For example, Appending \(aqk\(aq or \(aqK\(aq counts the
2649+number as kilobytes, \(aqm\(aq or \(aqM\(aq makes it megabytes, while \(aqg\(aq or \(aqG\(aq makes it
2650+gigabytes. Examples: 200K, 3m and 1G. (Added in 7.58.0)
2651+
2652+\fBNOTE\fP: before curl 8.4.0, when the file size is not known prior to
2653+download, for such files this option has no effect even if the file transfer
2654+ends up being larger than this given limit.
2655+
2656+Starting with curl 8.4.0, this option aborts the transfer if it reaches the
2657+threshold during transfer.
2658+
2659+If --max-filesize is provided several times, the last set value is used.
2660+
2661+Example:
2662+.nf
2663+ curl --max-filesize 100K https://example.com
2664+.fi
2665+
2666+See also \fI\-\-limit\-rate\fP.
2667+.IP "\-\-max\-redirs <num>"
2668+(HTTP) Set maximum number of redirections to follow. When \fI\-L, \-\-location\fP is used, to
2669+prevent curl from following too many redirects, by default, the limit is
2670+set to 50 redirects. Set this option to \-1 to make it unlimited.
2671+
2672+If --max-redirs is provided several times, the last set value is used.
2673+
2674+Example:
2675+.nf
2676+ curl --max-redirs 3 --location https://example.com
2677+.fi
2678+
2679+See also \fI-L, \-\-location\fP.
2680+.IP "\-m, \-\-max\-time <fractional seconds>"
2681+Maximum time in seconds that you allow each transfer to take. This is useful
2682+for preventing your batch jobs from hanging for hours due to slow networks or
2683+links going down. This option accepts decimal values.
2684+
2685+If you enable retrying the transfer (\fI\-\-retry\fP) then the maximum time counter is
2686+reset each time the transfer is retried. You can use \fI\-\-retry\-max\-time\fP to limit
2687+the retry time.
2688+
2689+The decimal value needs to provided using a dot (.) as decimal separator \- not
2690+the local version even if it might be using another separator.
2691+
2692+If --max-time is provided several times, the last set value is used.
2693+
2694+Examples:
2695+.nf
2696+ curl --max-time 10 https://example.com
2697+ curl --max-time 2.92 https://example.com
2698+.fi
2699+
2700+See also \fI\-\-connect\-timeout\fP and \fI\-\-retry\-max\-time\fP.
2701+.IP "\-\-metalink"
2702+This option was previously used to specify a Metalink resource. Metalink
2703+support is disabled in curl for security reasons (added in 7.78.0).
2704+
2705+If --metalink is provided several times, the last set value is used.
2706+
2707+Example:
2708+.nf
2709+ curl --metalink file https://example.com
2710+.fi
2711+
2712+See also \fI-Z, \-\-parallel\fP.
2713+.IP "\-\-negotiate"
2714+(HTTP) Enables Negotiate (SPNEGO) authentication.
2715+
2716+This option requires a library built with GSS\-API or SSPI support. Use
2717+\fI\-V, \-\-version\fP to see if your curl supports GSS\-API/SSPI or SPNEGO.
2718+
2719+When using this option, you must also provide a fake \fI\-u, \-\-user\fP option to activate
2720+the authentication code properly. Sending a \(aq\-u :\(aq is enough as the user name
2721+and password from the \fI\-u, \-\-user\fP option are not actually used.
2722+
2723+Providing --negotiate multiple times has no extra effect.
2724+
2725+Example:
2726+.nf
2727+ curl --negotiate -u : https://example.com
2728+.fi
2729+
2730+See also \fI\-\-basic\fP, \fI\-\-ntlm\fP, \fI\-\-anyauth\fP and \fI\-\-proxy\-negotiate\fP.
2731+.IP "\-\-netrc\-file <filename>"
2732+This option is similar to \fI\-n, \-\-netrc\fP, except that you provide the path (absolute
2733+or relative) to the netrc file that curl should use. You can only specify one
2734+netrc file per invocation.
2735+
2736+It abides by \fI\-\-netrc\-optional\fP if specified.
2737+
2738+If --netrc-file is provided several times, the last set value is used.
2739+
2740+Example:
2741+.nf
2742+ curl --netrc-file netrc https://example.com
2743+.fi
2744+
2745+See also \fI-n, \-\-netrc\fP, \fI-u, \-\-user\fP and \fI-K, \-\-config\fP. This option is mutually exclusive to \fI-n, \-\-netrc\fP.
2746+.IP "\-\-netrc\-optional"
2747+Similar to \fI\-n, \-\-netrc\fP, but this option makes the .netrc usage \fBoptional\fP
2748+and not mandatory as the \fI\-n, \-\-netrc\fP option does.
2749+
2750+Providing --netrc-optional multiple times has no extra effect.
2751+Disable it again with \-\-no-netrc-optional.
2752+
2753+Example:
2754+.nf
2755+ curl --netrc-optional https://example.com
2756+.fi
2757+
2758+See also \fI\-\-netrc\-file\fP. This option is mutually exclusive to \fI-n, \-\-netrc\fP.
2759+.IP "\-n, \-\-netrc"
2760+Makes curl scan the \fI.netrc\fP file in the user\(aqs home directory for login name
2761+and password. This is typically used for FTP on Unix. If used with HTTP, curl
2762+enables user authentication. See \fInetrc(5)\fP and \fIftp(1)\fP for details on the
2763+file format. Curl does not complain if that file does not have the right
2764+permissions (it should be neither world\- nor group\-readable). The environment
2765+variable "HOME" is used to find the home directory.
2766+
2767+On Windows two filenames in the home directory are checked: \fI.netrc\fP and
2768+\fI_netrc\fP, preferring the former. Older versions on Windows checked for \fI_netrc\fP
2769+only.
2770+
2771+A quick and simple example of how to setup a \fI.netrc\fP to allow curl to FTP to
2772+the machine host.domain.com with user name \(aqmyself\(aq and password \(aqsecret\(aq
2773+could look similar to:
2774+.nf
2775+
2776+machine host.domain.com
2777+login myself
2778+password secret
2779+
2780+Providing --netrc multiple times has no extra effect.
2781+Disable it again with \-\-no-netrc.
2782+
2783+Example:
2784+.nf
2785+ curl --netrc https://example.com
2786+.fi
2787+
2788+See also \fI\-\-netrc\-file\fP, \fI-K, \-\-config\fP and \fI-u, \-\-user\fP. This option is mutually exclusive to \fI\-\-netrc\-file\fP and \fI\-\-netrc\-optional\fP.
2789+.IP "\-:, \-\-next"
2790+Tells curl to use a separate operation for the following URL and associated
2791+options. This allows you to send several URL requests, each with their own
2792+specific options, for example, such as different user names or custom requests
2793+for each.
2794+
2795+\fI\-:, \-\-next\fP resets all local options and only global ones have their values survive
2796+over to the operation following the \fI\-:, \-\-next\fP instruction. Global options include
2797+\fI\-v, \-\-verbose\fP, \fI\-\-trace\fP, \fI\-\-trace\-ascii\fP and \fI\-\-fail\-early\fP.
2798+
2799+For example, you can do both a GET and a POST in a single command line:
2800+.nf
2801+
2802+curl www1.example.com \--next \-d postthis www2.example.com
2803+
2804+--next can be used several times in a command line
2805+
2806+Examples:
2807+.nf
2808+ curl https://example.com --next -d postthis www2.example.com
2809+ curl -I https://example.com --next https://example.net/
2810+.fi
2811+
2812+See also \fI-Z, \-\-parallel\fP and \fI-K, \-\-config\fP.
2813+.IP "\-\-no\-alpn"
2814+(HTTPS) Disable the ALPN TLS extension. ALPN is enabled by default if libcurl was built
2815+with an SSL library that supports ALPN. ALPN is used by a libcurl that supports
2816+HTTP/2 to negotiate HTTP/2 support with the server during https sessions.
2817+
2818+Note that this is the negated option name documented. You can use \--alpn to
2819+enable ALPN.
2820+
2821+Providing --no-alpn multiple times has no extra effect.
2822+Disable it again with \-\-alpn.
2823+
2824+Example:
2825+.nf
2826+ curl --no-alpn https://example.com
2827+.fi
2828+
2829+See also \fI\-\-no\-npn\fP and \fI\-\-http2\fP. \fI\-\-no\-alpn\fP requires that the underlying libcurl was built to support TLS.
2830+.IP "\-N, \-\-no\-buffer"
2831+Disables the buffering of the output stream. In normal work situations, curl
2832+uses a standard buffered output stream that has the effect that it outputs the
2833+data in chunks, not necessarily exactly when the data arrives. Using this
2834+option disables that buffering.
2835+
2836+Note that this is the negated option name documented. You can use \--buffer to
2837+enable buffering again.
2838+
2839+Providing --no-buffer multiple times has no extra effect.
2840+Disable it again with \-\-buffer.
2841+
2842+Example:
2843+.nf
2844+ curl --no-buffer https://example.com
2845+.fi
2846+
2847+See also \fI-#, \-\-progress\-bar\fP.
2848+.IP "\-\-no\-clobber"
2849+When used in conjunction with the \fI\-o, \-\-output\fP, \fI\-J, \-\-remote\-header\-name\fP,
2850+\fI\-O, \-\-remote\-name\fP, or \fI\-\-remote\-name\-all\fP options, curl avoids overwriting files
2851+that already exist. Instead, a dot and a number gets appended to the name of
2852+the file that would be created, up to filename.100 after which it does not
2853+create any file.
2854+
2855+Note that this is the negated option name documented. You can thus use
2856+-\-clobber to enforce the clobbering, even if \fI\-J, \-\-remote\-header\-name\fP is
2857+specified.
2858+
2859+Providing --no-clobber multiple times has no extra effect.
2860+Disable it again with \-\-clobber.
2861+
2862+Example:
2863+.nf
2864+ curl --no-clobber --output local/dir/file https://example.com
2865+.fi
2866+
2867+See also \fI-o, \-\-output\fP and \fI-O, \-\-remote\-name\fP. Added in 7.83.0.
2868+.IP "\-\-no\-keepalive"
2869+Disables the use of keepalive messages on the TCP connection. curl otherwise
2870+enables them by default.
2871+
2872+Note that this is the negated option name documented. You can thus use
2873+-\-keepalive to enforce keepalive.
2874+
2875+Providing --no-keepalive multiple times has no extra effect.
2876+Disable it again with \-\-keepalive.
2877+
2878+Example:
2879+.nf
2880+ curl --no-keepalive https://example.com
2881+.fi
2882+
2883+See also \fI\-\-keepalive\-time\fP.
2884+.IP "\-\-no\-npn"
2885+(HTTPS) curl never uses NPN, this option has no effect (added in 7.86.0).
2886+
2887+Disable the NPN TLS extension. NPN is enabled by default if libcurl was built
2888+with an SSL library that supports NPN. NPN is used by a libcurl that supports
2889+HTTP/2 to negotiate HTTP/2 support with the server during https sessions.
2890+
2891+Providing --no-npn multiple times has no extra effect.
2892+Disable it again with \-\-npn.
2893+
2894+Example:
2895+.nf
2896+ curl --no-npn https://example.com
2897+.fi
2898+
2899+See also \fI\-\-no\-alpn\fP and \fI\-\-http2\fP. \fI\-\-no\-npn\fP requires that the underlying libcurl was built to support TLS.
2900+.IP "\-\-no\-progress\-meter"
2901+Option to switch off the progress meter output without muting or otherwise
2902+affecting warning and informational messages like \fI\-s, \-\-silent\fP does.
2903+
2904+Note that this is the negated option name documented. You can thus use
2905+-\-progress\-meter to enable the progress meter again.
2906+
2907+Providing --no-progress-meter multiple times has no extra effect.
2908+Disable it again with \-\-progress-meter.
2909+
2910+Example:
2911+.nf
2912+ curl --no-progress-meter -o store https://example.com
2913+.fi
2914+
2915+See also \fI-v, \-\-verbose\fP and \fI-s, \-\-silent\fP. Added in 7.67.0.
2916+.IP "\-\-no\-sessionid"
2917+(TLS) Disable curl\(aqs use of SSL session\-ID caching. By default all transfers are
2918+done using the cache. Note that while nothing should ever get hurt by
2919+attempting to reuse SSL session\-IDs, there seem to be broken SSL
2920+implementations in the wild that may require you to disable this in order for
2921+you to succeed.
2922+
2923+Note that this is the negated option name documented. You can thus use
2924+-\-sessionid to enforce session\-ID caching.
2925+
2926+Providing --no-sessionid multiple times has no extra effect.
2927+Disable it again with \-\-sessionid.
2928+
2929+Example:
2930+.nf
2931+ curl --no-sessionid https://example.com
2932+.fi
2933+
2934+See also \fI-k, \-\-insecure\fP.
2935+.IP "\-\-noproxy <no\-proxy\-list>"
2936+Comma\-separated list of hosts for which not to use a proxy, if one is
2937+specified. The only wildcard is a single "*" character, which matches all
2938+hosts, and effectively disables the proxy. Each name in this list is matched
2939+as either a domain which contains the hostname, or the hostname itself. For
2940+example, "local.com" would match "local.com", "local.com:80", and
2941+\&"www.local.com", but not "www.notlocal.com".
2942+
2943+This option overrides the environment variables that disable the proxy
2944+("no_proxy" and "NO_PROXY") (added in 7.53.0). If there is an environment
2945+variable disabling a proxy, you can set the no proxy list to "" to override
2946+it.
2947+
2948+IP addresses specified to this option can be provided using CIDR notation
2949+(added in 7.86.0): an appended slash and number specifies the number of
2950+network bits out of the address to use in the comparison. For example
2951+\&"192.168.0.0/16" would match all addresses starting with "192.168".
2952+
2953+If --noproxy is provided several times, the last set value is used.
2954+
2955+Example:
2956+.nf
2957+ curl --noproxy "www.example" https://example.com
2958+.fi
2959+
2960+See also \fI-x, \-\-proxy\fP.
2961+.IP "\-\-ntlm\-wb"
2962+(HTTP) Enables NTLM much in the style \fI\-\-ntlm\fP does, but hand over the authentication
2963+to the separate binary "ntlmauth" application that is executed when needed.
2964+
2965+Providing --ntlm-wb multiple times has no extra effect.
2966+
2967+Example:
2968+.nf
2969+ curl --ntlm-wb -u user:password https://example.com
2970+.fi
2971+
2972+See also \fI\-\-ntlm\fP and \fI\-\-proxy\-ntlm\fP.
2973+.IP "\-\-ntlm"
2974+(HTTP) Enables NTLM authentication. The NTLM authentication method was designed by
2975+Microsoft and is used by IIS web servers. It is a proprietary protocol,
2976+reverse\-engineered by clever people and implemented in curl based on their
2977+efforts. This kind of behavior should not be endorsed, you should encourage
2978+everyone who uses NTLM to switch to a public and documented authentication
2979+method instead, such as Digest.
2980+
2981+If you want to enable NTLM for your proxy authentication, then use
2982+\fI\-\-proxy\-ntlm\fP.
2983+
2984+Providing --ntlm multiple times has no extra effect.
2985+
2986+Example:
2987+.nf
2988+ curl --ntlm -u user:password https://example.com
2989+.fi
2990+
2991+See also \fI\-\-proxy\-ntlm\fP. \fI\-\-ntlm\fP requires that the underlying libcurl was built to support TLS. This option is mutually exclusive to \fI\-\-basic\fP and \fI\-\-negotiate\fP and \fI\-\-digest\fP and \fI\-\-anyauth\fP.
2992+.IP "\-\-oauth2\-bearer <token>"
2993+(IMAP LDAP POP3 SMTP HTTP) Specify the Bearer Token for OAUTH 2.0 server authentication. The Bearer Token
2994+is used in conjunction with the user name which can be specified as part of
2995+the \fI\-\-url\fP or \fI\-u, \-\-user\fP options.
2996+
2997+The Bearer Token and user name are formatted according to RFC 6750.
2998+
2999+If --oauth2-bearer is provided several times, the last set value is used.
3000+
3001+Example:
3002+.nf
3003+ curl --oauth2-bearer "mF_9.B5f-4.1JqM" https://example.com
3004+.fi
3005+
3006+See also \fI\-\-basic\fP, \fI\-\-ntlm\fP and \fI\-\-digest\fP.
3007+.IP "\-\-output\-dir <dir>"
3008+This option specifies the directory in which files should be stored, when
3009+\fI\-O, \-\-remote\-name\fP or \fI\-o, \-\-output\fP are used.
3010+
3011+The given output directory is used for all URLs and output options on the
3012+command line, up until the first \fI\-:, \-\-next\fP.
3013+
3014+If the specified target directory does not exist, the operation fails unless
3015+\fI\-\-create\-dirs\fP is also used.
3016+
3017+If --output-dir is provided several times, the last set value is used.
3018+
3019+Example:
3020+.nf
3021+ curl --output-dir "tmp" -O https://example.com
3022+.fi
3023+
3024+See also \fI-O, \-\-remote\-name\fP and \fI-J, \-\-remote\-header\-name\fP. Added in 7.73.0.
3025+.IP "\-o, \-\-output <file>"
3026+Write output to <file> instead of stdout. If you are using {} or [] to fetch
3027+multiple documents, you should quote the URL and you can use \(aq#\(aq followed by a
3028+number in the <file> specifier. That variable is replaced with the current
3029+string for the URL being fetched. Like in:
3030+.nf
3031+
3032+curl "http://{one,two}.example.com" \-o "file_#1.txt"
3033+.fi
3034+
3035+or use several variables like:
3036+.nf
3037+
3038+curl "http://{site,host}.host[1\-5].example" \-o "#1_#2"
3039+.fi
3040+
3041+You may use this option as many times as the number of URLs you have. For
3042+example, if you specify two URLs on the same command line, you can use it like
3043+this:
3044+.nf
3045+
3046+curl \-o aa example.com \-o bb example.net
3047+.fi
3048+
3049+and the order of the \-o options and the URLs does not matter, just that the
3050+first \-o is for the first URL and so on, so the above command line can also be
3051+written as
3052+.nf
3053+
3054+curl example.com example.net \-o aa \-o bb
3055+.fi
3056+
3057+See also the \fI\-\-create\-dirs\fP option to create the local directories
3058+dynamically. Specifying the output as \(aq\-\(aq (a single dash) passes the output to
3059+stdout.
3060+
3061+To suppress response bodies, you can redirect output to /dev/null:
3062+.nf
3063+
3064+curl example.com \-o /dev/null
3065+.fi
3066+
3067+Or for Windows:
3068+.nf
3069+
3070+curl example.com \-o nul
3071+
3072+--output can be used several times in a command line
3073+
3074+Examples:
3075+.nf
3076+ curl -o file https://example.com
3077+ curl "http://{one,two}.example.com" -o "file_#1.txt"
3078+ curl "http://{site,host}.host[1-5].example" -o "#1_#2"
3079+ curl -o file https://example.com -o file2 https://example.net
3080+.fi
3081+
3082+See also \fI-O, \-\-remote\-name\fP, \fI\-\-remote\-name\-all\fP and \fI-J, \-\-remote\-header\-name\fP.
3083+.IP "\-\-parallel\-immediate"
3084+When doing parallel transfers, this option instructs curl that it should
3085+rather prefer opening up more connections in parallel at once rather than
3086+waiting to see if new transfers can be added as multiplexed streams on another
3087+connection.
3088+
3089+This option is global and does not need to be specified for each use of --next.
3090+
3091+Providing --parallel-immediate multiple times has no extra effect.
3092+Disable it again with \-\-no-parallel-immediate.
3093+
3094+Example:
3095+.nf
3096+ curl --parallel-immediate -Z https://example.com -o file1 https://example.com -o file2
3097+.fi
3098+
3099+See also \fI-Z, \-\-parallel\fP and \fI\-\-parallel\-max\fP. Added in 7.68.0.
3100+.IP "\-\-parallel\-max <num>"
3101+When asked to do parallel transfers, using \fI\-Z, \-\-parallel\fP, this option controls
3102+the maximum amount of transfers to do simultaneously.
3103+
3104+This option is global and does not need to be specified for each use of
3105+\fI\-:, \-\-next\fP.
3106+
3107+The default is 50.
3108+
3109+If --parallel-max is provided several times, the last set value is used.
3110+
3111+Example:
3112+.nf
3113+ curl --parallel-max 100 -Z https://example.com ftp://example.com/
3114+.fi
3115+
3116+See also \fI-Z, \-\-parallel\fP. Added in 7.66.0.
3117+.IP "\-Z, \-\-parallel"
3118+Makes curl perform its transfers in parallel as compared to the regular serial
3119+manner.
3120+
3121+This option is global and does not need to be specified for each use of --next.
3122+
3123+Providing --parallel multiple times has no extra effect.
3124+Disable it again with \-\-no-parallel.
3125+
3126+Example:
3127+.nf
3128+ curl --parallel https://example.com -o file1 https://example.com -o file2
3129+.fi
3130+
3131+See also \fI-:, \-\-next\fP and \fI-v, \-\-verbose\fP. Added in 7.66.0.
3132+.IP "\-\-pass <phrase>"
3133+(SSH TLS) Passphrase for the private key.
3134+
3135+If --pass is provided several times, the last set value is used.
3136+
3137+Example:
3138+.nf
3139+ curl --pass secret --key file https://example.com
3140+.fi
3141+
3142+See also \fI\-\-key\fP and \fI-u, \-\-user\fP.
3143+.IP "\-\-path\-as\-is"
3144+Tell curl to not handle sequences of /../ or /./ in the given URL
3145+path. Normally curl squashes or merges them according to standards but with
3146+this option set you tell it not to do that.
3147+
3148+Providing --path-as-is multiple times has no extra effect.
3149+Disable it again with \-\-no-path-as-is.
3150+
3151+Example:
3152+.nf
3153+ curl --path-as-is https://example.com/../../etc/passwd
3154+.fi
3155+
3156+See also \fI\-\-request\-target\fP.
3157+.IP "\-\-pinnedpubkey <hashes>"
3158+(TLS) Tells curl to use the specified public key file (or hashes) to verify the
3159+peer. This can be a path to a file which contains a single public key in PEM
3160+or DER format, or any number of base64 encoded sha256 hashes preceded by
3161+\(aqsha256//\(aq and separated by \(aq;\(aq.
3162+
3163+When negotiating a TLS or SSL connection, the server sends a certificate
3164+indicating its identity. A public key is extracted from this certificate and
3165+if it does not exactly match the public key provided to this option, curl
3166+aborts the connection before sending or receiving any data.
3167+
3168+This option is independent of option \fI\-k, \-\-insecure\fP. If you use both options
3169+together then the peer is still verified by public key.
3170+
3171+PEM/DER support:
3172+
3173+OpenSSL and GnuTLS, wolfSSL (added in 7.43.0), mbedTLS
3174+, Secure Transport macOS 10.7+/iOS 10+ (7.54.1), Schannel
3175+(7.58.1)
3176+
3177+sha256 support:
3178+
3179+OpenSSL, GnuTLS and wolfSSL, mbedTLS (added in 7.47.0),
3180+Secure Transport macOS 10.7+/iOS 10+ (7.54.1), Schannel (7.58.1)
3181+
3182+Other SSL backends not supported.
3183+
3184+If --pinnedpubkey is provided several times, the last set value is used.
3185+
3186+Examples:
3187+.nf
3188+ curl --pinnedpubkey keyfile https://example.com
3189+ curl --pinnedpubkey 'sha256//ce118b51897f4452dc' https://example.com
3190+.fi
3191+
3192+See also \fI\-\-hostpubsha256\fP.
3193+.IP "\-\-post301"
3194+(HTTP) Tells curl to respect RFC 7231/6.4.2 and not convert POST requests into GET
3195+requests when following a 301 redirection. The non\-RFC behavior is ubiquitous
3196+in web browsers, so curl does the conversion by default to maintain
3197+consistency. However, a server may require a POST to remain a POST after such
3198+a redirection. This option is meaningful only when using \fI\-L, \-\-location\fP.
3199+
3200+Providing --post301 multiple times has no extra effect.
3201+Disable it again with \-\-no-post301.
3202+
3203+Example:
3204+.nf
3205+ curl --post301 --location -d "data" https://example.com
3206+.fi
3207+
3208+See also \fI\-\-post302\fP, \fI\-\-post303\fP and \fI-L, \-\-location\fP.
3209+.IP "\-\-post302"
3210+(HTTP) Tells curl to respect RFC 7231/6.4.3 and not convert POST requests into GET
3211+requests when following a 302 redirection. The non\-RFC behavior is ubiquitous
3212+in web browsers, so curl does the conversion by default to maintain
3213+consistency. However, a server may require a POST to remain a POST after such
3214+a redirection. This option is meaningful only when using \fI\-L, \-\-location\fP.
3215+
3216+Providing --post302 multiple times has no extra effect.
3217+Disable it again with \-\-no-post302.
3218+
3219+Example:
3220+.nf
3221+ curl --post302 --location -d "data" https://example.com
3222+.fi
3223+
3224+See also \fI\-\-post301\fP, \fI\-\-post303\fP and \fI-L, \-\-location\fP.
3225+.IP "\-\-post303"
3226+(HTTP) Tells curl to violate RFC 7231/6.4.4 and not convert POST requests into GET
3227+requests when following 303 redirections. A server may require a POST to
3228+remain a POST after a 303 redirection. This option is meaningful only when
3229+using \fI\-L, \-\-location\fP.
3230+
3231+Providing --post303 multiple times has no extra effect.
3232+Disable it again with \-\-no-post303.
3233+
3234+Example:
3235+.nf
3236+ curl --post303 --location -d "data" https://example.com
3237+.fi
3238+
3239+See also \fI\-\-post302\fP, \fI\-\-post301\fP and \fI-L, \-\-location\fP.
3240+.IP "\-\-preproxy [protocol://]host[:port]"
3241+Use the specified SOCKS proxy before connecting to an HTTP or HTTPS \fI\-x, \-\-proxy\fP. In
3242+such a case curl first connects to the SOCKS proxy and then connects (through
3243+SOCKS) to the HTTP or HTTPS proxy. Hence pre proxy.
3244+
3245+The pre proxy string should be specified with a protocol:// prefix to specify
3246+alternative proxy protocols. Use socks4://, socks4a://, socks5:// or
3247+socks5h:// to request the specific SOCKS version to be used. No protocol
3248+specified makes curl default to SOCKS4.
3249+
3250+If the port number is not specified in the proxy string, it is assumed to be
3251+1080.
3252+
3253+User and password that might be provided in the proxy string are URL decoded
3254+by curl. This allows you to pass in special characters such as @ by using %40
3255+or pass in a colon with %3a.
3256+
3257+If --preproxy is provided several times, the last set value is used.
3258+
3259+Example:
3260+.nf
3261+ curl --preproxy socks5://proxy.example -x http://http.example https://example.com
3262+.fi
3263+
3264+See also \fI-x, \-\-proxy\fP and \fI\-\-socks5\fP. Added in 7.52.0.
3265+.IP "\-#, \-\-progress\-bar"
3266+Make curl display transfer progress as a simple progress bar instead of the
3267+standard, more informational, meter.
3268+
3269+This progress bar draws a single line of \(aq#\(aq characters across the screen and
3270+shows a percentage if the transfer size is known. For transfers without a
3271+known size, there is a space ship (\-=o=\-) that moves back and forth but only
3272+while data is being transferred, with a set of flying hash sign symbols on
3273+top.
3274+
3275+This option is global and does not need to be specified for each use of --next.
3276+
3277+Providing --progress-bar multiple times has no extra effect.
3278+Disable it again with \-\-no-progress-bar.
3279+
3280+Example:
3281+.nf
3282+ curl -# -O https://example.com
3283+.fi
3284+
3285+See also \fI\-\-styled\-output\fP.
3286+.IP "\-\-proto\-default <protocol>"
3287+Tells curl to use \fIprotocol\fP for any URL missing a scheme name.
3288+
3289+An unknown or unsupported protocol causes error
3290+\fICURLE_UNSUPPORTED_PROTOCOL\fP (1).
3291+
3292+This option does not change the default proxy protocol (http).
3293+
3294+Without this option set, curl guesses protocol based on the host name, see
3295+\fI\-\-url\fP for details.
3296+
3297+If --proto-default is provided several times, the last set value is used.
3298+
3299+Example:
3300+.nf
3301+ curl --proto-default https ftp.example.com
3302+.fi
3303+
3304+See also \fI\-\-proto\fP and \fI\-\-proto\-redir\fP.
3305+.IP "\-\-proto\-redir <protocols>"
3306+Tells curl to limit what protocols it may use on redirect. Protocols denied by
3307+\fI\-\-proto\fP are not overridden by this option. See \fI\-\-proto\fP for how protocols are
3308+represented.
3309+
3310+Example, allow only HTTP and HTTPS on redirect:
3311+.nf
3312+
3313+curl \--proto\-redir \-all,http,https http://example.com
3314+.fi
3315+
3316+By default curl only allows HTTP, HTTPS, FTP and FTPS on redirects (added in
3317+7.65.2). Specifying \fIall\fP or \fI+all\fP enables all protocols on redirects, which
3318+is not good for security.
3319+
3320+If --proto-redir is provided several times, the last set value is used.
3321+
3322+Example:
3323+.nf
3324+ curl --proto-redir =http,https https://example.com
3325+.fi
3326+
3327+See also \fI\-\-proto\fP.
3328+.IP "\-\-proto <protocols>"
3329+Tells curl to limit what protocols it may use for transfers. Protocols are
3330+evaluated left to right, are comma separated, and are each a protocol name or
3331+\(aqall\(aq, optionally prefixed by zero or more modifiers. Available modifiers are:
3332+.RS
3333+.IP +
3334+Permit this protocol in addition to protocols already permitted (this is
3335+the default if no modifier is used).
3336+.IP -
3337+Deny this protocol, removing it from the list of protocols already permitted.
3338+.IP =
3339+Permit only this protocol (ignoring the list already permitted), though
3340+subject to later modification by subsequent entries in the comma separated
3341+list.
3342+.RE
3343+.IP
3344+For example: \fI\-\-proto\fP \-ftps uses the default protocols, but disables ftps
3345+
3346+\fI\-\-proto\fP \-all,https,+http only enables http and https
3347+
3348+\fI\-\-proto\fP =http,https also only enables http and https
3349+
3350+Unknown and disabled protocols produce a warning. This allows scripts to
3351+safely rely on being able to disable potentially dangerous protocols, without
3352+relying upon support for that protocol being built into curl to avoid an error.
3353+
3354+This option can be used multiple times, in which case the effect is the same
3355+as concatenating the protocols into one instance of the option.
3356+.RE
3357+.IP
3358+
3359+If --proto is provided several times, the last set value is used.
3360+
3361+Example:
3362+.nf
3363+ curl --proto =http,https,sftp https://example.com
3364+.fi
3365+
3366+See also \fI\-\-proto\-redir\fP and \fI\-\-proto\-default\fP.
3367+.IP "\-\-proxy\-anyauth"
3368+Tells curl to pick a suitable authentication method when communicating with
3369+the given HTTP proxy. This might cause an extra request/response round\-trip.
3370+
3371+Providing --proxy-anyauth multiple times has no extra effect.
3372+
3373+Example:
3374+.nf
3375+ curl --proxy-anyauth --proxy-user user:passwd -x proxy https://example.com
3376+.fi
3377+
3378+See also \fI-x, \-\-proxy\fP, \fI\-\-proxy\-basic\fP and \fI\-\-proxy\-digest\fP.
3379+.IP "\-\-proxy\-basic"
3380+Tells curl to use HTTP Basic authentication when communicating with the given
3381+proxy. Use \fI\-\-basic\fP for enabling HTTP Basic with a remote host. Basic is the
3382+default authentication method curl uses with proxies.
3383+
3384+Providing --proxy-basic multiple times has no extra effect.
3385+
3386+Example:
3387+.nf
3388+ curl --proxy-basic --proxy-user user:passwd -x proxy https://example.com
3389+.fi
3390+
3391+See also \fI-x, \-\-proxy\fP, \fI\-\-proxy\-anyauth\fP and \fI\-\-proxy\-digest\fP.
3392+.IP "\-\-proxy\-ca\-native"
3393+(TLS) Tells curl to use the CA store from the native operating system to verify the
3394+HTTPS proxy. By default, curl uses a CA store provided in a single file or
3395+directory, but when using this option it interfaces the operating system\(aqs own
3396+vault.
3397+
3398+This option works for curl on Windows when built to use OpenSSL, wolfSSL
3399+(added in 8.3.0) or GnuTLS (added in 8.5.0). When curl on Windows is built to
3400+use Schannel, this feature is implied and curl then only uses the native CA
3401+store.
3402+
3403+Providing --proxy-ca-native multiple times has no extra effect.
3404+Disable it again with \-\-no-proxy-ca-native.
3405+
3406+Example:
3407+.nf
3408+ curl --ca-native https://example.com
3409+.fi
3410+
3411+See also \fI\-\-cacert\fP, \fI\-\-capath\fP and \fI-k, \-\-insecure\fP. Added in 8.2.0.
3412+.IP "\-\-proxy\-cacert <file>"
3413+Same as \fI\-\-cacert\fP but used in HTTPS proxy context.
3414+
3415+If --proxy-cacert is provided several times, the last set value is used.
3416+
3417+Example:
3418+.nf
3419+ curl --proxy-cacert CA-file.txt -x https://proxy https://example.com
3420+.fi
3421+
3422+See also \fI\-\-proxy\-capath\fP, \fI\-\-cacert\fP, \fI\-\-capath\fP and \fI-x, \-\-proxy\fP. Added in 7.52.0.
3423+.IP "\-\-proxy\-capath <dir>"
3424+Same as \fI\-\-capath\fP but used in HTTPS proxy context.
3425+
3426+If --proxy-capath is provided several times, the last set value is used.
3427+
3428+Example:
3429+.nf
3430+ curl --proxy-capath /local/directory -x https://proxy https://example.com
3431+.fi
3432+
3433+See also \fI\-\-proxy\-cacert\fP, \fI-x, \-\-proxy\fP and \fI\-\-capath\fP. Added in 7.52.0.
3434+.IP "\-\-proxy\-cert\-type <type>"
3435+Same as \fI\-\-cert\-type\fP but used in HTTPS proxy context.
3436+
3437+If --proxy-cert-type is provided several times, the last set value is used.
3438+
3439+Example:
3440+.nf
3441+ curl --proxy-cert-type PEM --proxy-cert file -x https://proxy https://example.com
3442+.fi
3443+
3444+See also \fI\-\-proxy\-cert\fP. Added in 7.52.0.
3445+.IP "\-\-proxy\-cert <cert[:passwd]>"
3446+Same as \fI\-E, \-\-cert\fP but used in HTTPS proxy context.
3447+
3448+If --proxy-cert is provided several times, the last set value is used.
3449+
3450+Example:
3451+.nf
3452+ curl --proxy-cert file -x https://proxy https://example.com
3453+.fi
3454+
3455+See also \fI\-\-proxy\-cert\-type\fP. Added in 7.52.0.
3456+.IP "\-\-proxy\-ciphers <list>"
3457+Same as \fI\-\-ciphers\fP but used in HTTPS proxy context.
3458+
3459+Specifies which ciphers to use in the connection to the HTTPS proxy. The list
3460+of ciphers must specify valid ciphers. Read up on SSL cipher list details on
3461+this URL:
3462+
3463+https://curl.se/docs/ssl\-ciphers.html
3464+
3465+If --proxy-ciphers is provided several times, the last set value is used.
3466+
3467+Example:
3468+.nf
3469+ curl --proxy-ciphers ECDHE-ECDSA-AES256-CCM8 -x https://proxy https://example.com
3470+.fi
3471+
3472+See also \fI\-\-ciphers\fP, \fI\-\-curves\fP and \fI-x, \-\-proxy\fP. Added in 7.52.0.
3473+.IP "\-\-proxy\-crlfile <file>"
3474+Same as \fI\-\-crlfile\fP but used in HTTPS proxy context.
3475+
3476+If --proxy-crlfile is provided several times, the last set value is used.
3477+
3478+Example:
3479+.nf
3480+ curl --proxy-crlfile rejects.txt -x https://proxy https://example.com
3481+.fi
3482+
3483+See also \fI\-\-crlfile\fP and \fI-x, \-\-proxy\fP. Added in 7.52.0.
3484+.IP "\-\-proxy\-digest"
3485+Tells curl to use HTTP Digest authentication when communicating with the given
3486+proxy. Use \fI\-\-digest\fP for enabling HTTP Digest with a remote host.
3487+
3488+Providing --proxy-digest multiple times has no extra effect.
3489+
3490+Example:
3491+.nf
3492+ curl --proxy-digest --proxy-user user:passwd -x proxy https://example.com
3493+.fi
3494+
3495+See also \fI-x, \-\-proxy\fP, \fI\-\-proxy\-anyauth\fP and \fI\-\-proxy\-basic\fP.
3496+.IP "\-\-proxy\-header <header/@file>"
3497+(HTTP) Extra header to include in the request when sending HTTP to a proxy. You may
3498+specify any number of extra headers. This is the equivalent option to \fI\-H, \-\-header\fP
3499+but is for proxy communication only like in CONNECT requests when you want a
3500+separate header sent to the proxy to what is sent to the actual remote host.
3501+
3502+curl makes sure that each header you add/replace is sent with the proper
3503+end\-of\-line marker, you should thus \fBnot\fP add that as a part of the header
3504+content: do not add newlines or carriage returns, they only mess things up for
3505+you.
3506+
3507+Headers specified with this option are not included in requests that curl
3508+knows are not be sent to a proxy.
3509+
3510+This option can take an argument in @filename style, which then adds a header
3511+for each line in the input file (added in 7.55.0). Using @\- makes curl read
3512+the headers from stdin.
3513+
3514+This option can be used multiple times to add/replace/remove multiple headers.
3515+
3516+--proxy-header can be used several times in a command line
3517+
3518+Examples:
3519+.nf
3520+ curl --proxy-header "X-First-Name: Joe" -x http://proxy https://example.com
3521+ curl --proxy-header "User-Agent: surprise" -x http://proxy https://example.com
3522+ curl --proxy-header "Host:" -x http://proxy https://example.com
3523+.fi
3524+
3525+See also \fI-x, \-\-proxy\fP.
3526+.IP "\-\-proxy\-http2"
3527+(HTTP) Tells curl to try negotiate HTTP version 2 with an HTTPS proxy. The proxy might
3528+still only offer HTTP/1 and then curl sticks to using that version.
3529+
3530+This has no effect for any other kinds of proxies.
3531+
3532+Providing --proxy-http2 multiple times has no extra effect.
3533+Disable it again with \-\-no-proxy-http2.
3534+
3535+Example:
3536+.nf
3537+ curl --proxy-http2 -x proxy https://example.com
3538+.fi
3539+
3540+See also \fI-x, \-\-proxy\fP. \fI\-\-proxy\-http2\fP requires that the underlying libcurl was built to support HTTP/2. Added in 8.1.0.
3541+.IP "\-\-proxy\-insecure"
3542+Same as \fI\-k, \-\-insecure\fP but used in HTTPS proxy context.
3543+
3544+Providing --proxy-insecure multiple times has no extra effect.
3545+Disable it again with \-\-no-proxy-insecure.
3546+
3547+Example:
3548+.nf
3549+ curl --proxy-insecure -x https://proxy https://example.com
3550+.fi
3551+
3552+See also \fI-x, \-\-proxy\fP and \fI-k, \-\-insecure\fP. Added in 7.52.0.
3553+.IP "\-\-proxy\-key\-type <type>"
3554+Same as \fI\-\-key\-type\fP but used in HTTPS proxy context.
3555+
3556+If --proxy-key-type is provided several times, the last set value is used.
3557+
3558+Example:
3559+.nf
3560+ curl --proxy-key-type DER --proxy-key here -x https://proxy https://example.com
3561+.fi
3562+
3563+See also \fI\-\-proxy\-key\fP and \fI-x, \-\-proxy\fP. Added in 7.52.0.
3564+.IP "\-\-proxy\-key <key>"
3565+Same as \fI\-\-key\fP but used in HTTPS proxy context.
3566+
3567+If --proxy-key is provided several times, the last set value is used.
3568+
3569+Example:
3570+.nf
3571+ curl --proxy-key here -x https://proxy https://example.com
3572+.fi
3573+
3574+See also \fI\-\-proxy\-key\-type\fP and \fI-x, \-\-proxy\fP. Added in 7.52.0.
3575+.IP "\-\-proxy\-negotiate"
3576+Tells curl to use HTTP Negotiate (SPNEGO) authentication when communicating
3577+with the given proxy. Use \fI\-\-negotiate\fP for enabling HTTP Negotiate (SPNEGO)
3578+with a remote host.
3579+
3580+Providing --proxy-negotiate multiple times has no extra effect.
3581+
3582+Example:
3583+.nf
3584+ curl --proxy-negotiate --proxy-user user:passwd -x proxy https://example.com
3585+.fi
3586+
3587+See also \fI\-\-proxy\-anyauth\fP and \fI\-\-proxy\-basic\fP.
3588+.IP "\-\-proxy\-ntlm"
3589+Tells curl to use HTTP NTLM authentication when communicating with the given
3590+proxy. Use \fI\-\-ntlm\fP for enabling NTLM with a remote host.
3591+
3592+Providing --proxy-ntlm multiple times has no extra effect.
3593+
3594+Example:
3595+.nf
3596+ curl --proxy-ntlm --proxy-user user:passwd -x http://proxy https://example.com
3597+.fi
3598+
3599+See also \fI\-\-proxy\-negotiate\fP and \fI\-\-proxy\-anyauth\fP.
3600+.IP "\-\-proxy\-pass <phrase>"
3601+Same as \fI\-\-pass\fP but used in HTTPS proxy context.
3602+
3603+If --proxy-pass is provided several times, the last set value is used.
3604+
3605+Example:
3606+.nf
3607+ curl --proxy-pass secret --proxy-key here -x https://proxy https://example.com
3608+.fi
3609+
3610+See also \fI-x, \-\-proxy\fP and \fI\-\-proxy\-key\fP. Added in 7.52.0.
3611+.IP "\-\-proxy\-pinnedpubkey <hashes>"
3612+(TLS) Tells curl to use the specified public key file (or hashes) to verify the
3613+proxy. This can be a path to a file which contains a single public key in PEM
3614+or DER format, or any number of base64 encoded sha256 hashes preceded by
3615+\(aqsha256//\(aq and separated by \(aq;\(aq.
3616+
3617+When negotiating a TLS or SSL connection, the server sends a certificate
3618+indicating its identity. A public key is extracted from this certificate and
3619+if it does not exactly match the public key provided to this option, curl
3620+aborts the connection before sending or receiving any data.
3621+
3622+If --proxy-pinnedpubkey is provided several times, the last set value is used.
3623+
3624+Examples:
3625+.nf
3626+ curl --proxy-pinnedpubkey keyfile https://example.com
3627+ curl --proxy-pinnedpubkey 'sha256//ce118b51897f4452dc' https://example.com
3628+.fi
3629+
3630+See also \fI\-\-pinnedpubkey\fP and \fI-x, \-\-proxy\fP. Added in 7.59.0.
3631+.IP "\-\-proxy\-service\-name <name>"
3632+This option allows you to change the service name for proxy negotiation.
3633+
3634+If --proxy-service-name is provided several times, the last set value is used.
3635+
3636+Example:
3637+.nf
3638+ curl --proxy-service-name "shrubbery" -x proxy https://example.com
3639+.fi
3640+
3641+See also \fI\-\-service\-name\fP and \fI-x, \-\-proxy\fP.
3642+.IP "\-\-proxy\-ssl\-allow\-beast"
3643+Same as \fI\-\-ssl\-allow\-beast\fP but used in HTTPS proxy context.
3644+
3645+Providing --proxy-ssl-allow-beast multiple times has no extra effect.
3646+Disable it again with \-\-no-proxy-ssl-allow-beast.
3647+
3648+Example:
3649+.nf
3650+ curl --proxy-ssl-allow-beast -x https://proxy https://example.com
3651+.fi
3652+
3653+See also \fI\-\-ssl\-allow\-beast\fP and \fI-x, \-\-proxy\fP. Added in 7.52.0.
3654+.IP "\-\-proxy\-ssl\-auto\-client\-cert"
3655+Same as \fI\-\-ssl\-auto\-client\-cert\fP but used in HTTPS proxy context.
3656+
3657+Providing --proxy-ssl-auto-client-cert multiple times has no extra effect.
3658+Disable it again with \-\-no-proxy-ssl-auto-client-cert.
3659+
3660+Example:
3661+.nf
3662+ curl --proxy-ssl-auto-client-cert -x https://proxy https://example.com
3663+.fi
3664+
3665+See also \fI\-\-ssl\-auto\-client\-cert\fP and \fI-x, \-\-proxy\fP. Added in 7.77.0.
3666+.IP "\-\-proxy\-tls13\-ciphers <ciphersuite list>"
3667+(TLS) Specifies which cipher suites to use in the connection to your HTTPS proxy
3668+when it negotiates TLS 1.3. The list of ciphers suites must specify valid
3669+ciphers. Read up on TLS 1.3 cipher suite details on this URL:
3670+
3671+https://curl.se/docs/ssl\-ciphers.html
3672+
3673+This option is currently used only when curl is built to use OpenSSL 1.1.1 or
3674+later. If you are using a different SSL backend you can try setting TLS 1.3
3675+cipher suites by using the \fI\-\-proxy\-ciphers\fP option.
3676+
3677+If --proxy-tls13-ciphers is provided several times, the last set value is used.
3678+
3679+Example:
3680+.nf
3681+ curl --proxy-tls13-ciphers TLS_AES_128_GCM_SHA256 -x proxy https://example.com
3682+.fi
3683+
3684+See also \fI\-\-tls13\-ciphers\fP, \fI\-\-curves\fP and \fI\-\-proxy\-ciphers\fP. Added in 7.61.0.
3685+.IP "\-\-proxy\-tlsauthtype <type>"
3686+Same as \fI\-\-tlsauthtype\fP but used in HTTPS proxy context.
3687+
3688+If --proxy-tlsauthtype is provided several times, the last set value is used.
3689+
3690+Example:
3691+.nf
3692+ curl --proxy-tlsauthtype SRP -x https://proxy https://example.com
3693+.fi
3694+
3695+See also \fI-x, \-\-proxy\fP and \fI\-\-proxy\-tlsuser\fP. Added in 7.52.0.
3696+.IP "\-\-proxy\-tlspassword <string>"
3697+Same as \fI\-\-tlspassword\fP but used in HTTPS proxy context.
3698+
3699+If --proxy-tlspassword is provided several times, the last set value is used.
3700+
3701+Example:
3702+.nf
3703+ curl --proxy-tlspassword passwd -x https://proxy https://example.com
3704+.fi
3705+
3706+See also \fI-x, \-\-proxy\fP and \fI\-\-proxy\-tlsuser\fP. Added in 7.52.0.
3707+.IP "\-\-proxy\-tlsuser <name>"
3708+Same as \fI\-\-tlsuser\fP but used in HTTPS proxy context.
3709+
3710+If --proxy-tlsuser is provided several times, the last set value is used.
3711+
3712+Example:
3713+.nf
3714+ curl --proxy-tlsuser smith -x https://proxy https://example.com
3715+.fi
3716+
3717+See also \fI-x, \-\-proxy\fP and \fI\-\-proxy\-tlspassword\fP. Added in 7.52.0.
3718+.IP "\-\-proxy\-tlsv1"
3719+Same as \fI\-1, \-\-tlsv1\fP but used in HTTPS proxy context.
3720+
3721+Providing --proxy-tlsv1 multiple times has no extra effect.
3722+
3723+Example:
3724+.nf
3725+ curl --proxy-tlsv1 -x https://proxy https://example.com
3726+.fi
3727+
3728+See also \fI-x, \-\-proxy\fP. Added in 7.52.0.
3729+.IP "\-U, \-\-proxy\-user <user:password>"
3730+Specify the user name and password to use for proxy authentication.
3731+
3732+If you use a Windows SSPI\-enabled curl binary and do either Negotiate or NTLM
3733+authentication then you can tell curl to select the user name and password
3734+from your environment by specifying a single colon with this option: "\-U :".
3735+
3736+On systems where it works, curl hides the given option argument from process
3737+listings. This is not enough to protect credentials from possibly getting seen
3738+by other users on the same system as they still are visible for a moment
3739+before cleared. Such sensitive data should be retrieved from a file instead or
3740+similar and never used in clear text in a command line.
3741+
3742+If --proxy-user is provided several times, the last set value is used.
3743+
3744+Example:
3745+.nf
3746+ curl --proxy-user name:pwd -x proxy https://example.com
3747+.fi
3748+
3749+See also \fI\-\-proxy\-pass\fP.
3750+.IP "\-x, \-\-proxy [protocol://]host[:port]"
3751+Use the specified proxy.
3752+
3753+The proxy string can be specified with a protocol:// prefix. No protocol
3754+specified or http:// it is treated as an HTTP proxy. Use socks4://,
3755+socks4a://, socks5:// or socks5h:// to request a specific SOCKS version to be
3756+used.
3757+
3758+Unix domain sockets are supported for socks proxy. Set localhost for the host
3759+part. e.g. socks5h://localhost/path/to/socket.sock
3760+
3761+HTTPS proxy support works set with the https:// protocol prefix for OpenSSL
3762+and GnuTLS (added in 7.52.0). It also works for BearSSL, mbedTLS, rustls,
3763+Schannel, Secure Transport and wolfSSL (added in 7.87.0).
3764+
3765+Unrecognized and unsupported proxy protocols cause an error (added in 7.52.0).
3766+Ancient curl versions ignored unknown schemes and used http:// instead.
3767+
3768+If the port number is not specified in the proxy string, it is assumed to be
3769+1080.
3770+
3771+This option overrides existing environment variables that set the proxy to
3772+use. If there is an environment variable setting a proxy, you can set proxy to
3773+\&"" to override it.
3774+
3775+All operations that are performed over an HTTP proxy are transparently
3776+converted to HTTP. It means that certain protocol specific operations might
3777+not be available. This is not the case if you can tunnel through the proxy, as
3778+one with the \fI\-p, \-\-proxytunnel\fP option.
3779+
3780+User and password that might be provided in the proxy string are URL decoded
3781+by curl. This allows you to pass in special characters such as @ by using %40
3782+or pass in a colon with %3a.
3783+
3784+The proxy host can be specified the same way as the proxy environment
3785+variables, including the protocol prefix (http://) and the embedded user +
3786+password.
3787+
3788+When a proxy is used, the active FTP mode as set with \fI\-P, \-\-ftp\-port\fP, cannot be
3789+used.
3790+
3791+If --proxy is provided several times, the last set value is used.
3792+
3793+Example:
3794+.nf
3795+ curl --proxy http://proxy.example https://example.com
3796+.fi
3797+
3798+See also \fI\-\-socks5\fP and \fI\-\-proxy\-basic\fP.
3799+.IP "\-\-proxy1.0 <host[:port]>"
3800+Use the specified HTTP 1.0 proxy. If the port number is not specified, it is
3801+assumed at port 1080.
3802+
3803+The only difference between this and the HTTP proxy option \fI\-x, \-\-proxy\fP, is that
3804+attempts to use CONNECT through the proxy specifies an HTTP 1.0 protocol
3805+instead of the default HTTP 1.1.
3806+
3807+Providing --proxy1.0 multiple times has no extra effect.
3808+
3809+Example:
3810+.nf
3811+ curl --proxy1.0 -x http://proxy https://example.com
3812+.fi
3813+
3814+See also \fI-x, \-\-proxy\fP, \fI\-\-socks5\fP and \fI\-\-preproxy\fP.
3815+.IP "\-p, \-\-proxytunnel"
3816+When an HTTP proxy is used \fI\-x, \-\-proxy\fP, this option makes curl tunnel the traffic
3817+through the proxy. The tunnel approach is made with the HTTP proxy CONNECT
3818+request and requires that the proxy allows direct connect to the remote port
3819+number curl wants to tunnel through to.
3820+
3821+To suppress proxy CONNECT response headers when curl is set to output headers
3822+use \fI\-\-suppress\-connect\-headers\fP.
3823+
3824+Providing --proxytunnel multiple times has no extra effect.
3825+Disable it again with \-\-no-proxytunnel.
3826+
3827+Example:
3828+.nf
3829+ curl --proxytunnel -x http://proxy https://example.com
3830+.fi
3831+
3832+See also \fI-x, \-\-proxy\fP.
3833+.IP "\-\-pubkey <key>"
3834+(SFTP SCP) Public key file name. Allows you to provide your public key in this separate
3835+file.
3836+
3837+curl attempts to automatically extract the public key from the private key
3838+file, so passing this option is generally not required. Note that this public
3839+key extraction requires libcurl to be linked against a copy of libssh2 1.2.8
3840+or higher that is itself linked against OpenSSL.
3841+
3842+If --pubkey is provided several times, the last set value is used.
3843+
3844+Example:
3845+.nf
3846+ curl --pubkey file.pub sftp://example.com/
3847+.fi
3848+
3849+See also \fI\-\-pass\fP.
3850+.IP "\-Q, \-\-quote <command>"
3851+(FTP SFTP) Send an arbitrary command to the remote FTP or SFTP server. Quote commands are
3852+sent BEFORE the transfer takes place (just after the initial \fBPWD\fP command
3853+in an FTP transfer, to be exact). To make commands take place after a
3854+successful transfer, prefix them with a dash \(aq\-\(aq.
3855+
3856+(FTP only) To make commands be sent after curl has changed the working
3857+directory, just before the file transfer command(s), prefix the command with a
3858+\(aq+\(aq. This is not performed when a directory listing is performed.
3859+
3860+You may specify any number of commands.
3861+
3862+By default curl stops at first failure. To make curl continue even if the
3863+command fails, prefix the command with an asterisk (*). Otherwise, if the
3864+server returns failure for one of the commands, the entire operation is
3865+aborted.
3866+
3867+You must send syntactically correct FTP commands as RFC 959 defines to FTP
3868+servers, or one of the commands listed below to SFTP servers.
3869+
3870+SFTP is a binary protocol. Unlike for FTP, curl interprets SFTP quote commands
3871+itself before sending them to the server. File names may be quoted
3872+shell\-style to embed spaces or special characters. Following is the list of
3873+all supported SFTP quote commands:
3874+.RS
3875+.IP "atime date file"
3876+The atime command sets the last access time of the file named by the file
3877+operand. The <date expression> can be all sorts of date strings, see the
3878+\fIcurl_getdate(3)\fP man page for date expression details. (Added in 7.73.0)
3879+.IP "chgrp group file"
3880+The chgrp command sets the group ID of the file named by the file operand to
3881+the group ID specified by the group operand. The group operand is a decimal
3882+integer group ID.
3883+.IP "chmod mode file"
3884+The chmod command modifies the file mode bits of the specified file. The
3885+mode operand is an octal integer mode number.
3886+.IP "chown user file"
3887+The chown command sets the owner of the file named by the file operand to the
3888+user ID specified by the user operand. The user operand is a decimal
3889+integer user ID.
3890+.IP "ln source_file target_file"
3891+The ln and symlink commands create a symbolic link at the target_file location
3892+pointing to the source_file location.
3893+.IP "mkdir directory_name"
3894+The mkdir command creates the directory named by the directory_name operand.
3895+.IP "mtime date file"
3896+The mtime command sets the last modification time of the file named by the
3897+file operand. The <date expression> can be all sorts of date strings, see the
3898+\fIcurl_getdate(3)\fP man page for date expression details. (Added in 7.73.0)
3899+.IP pwd
3900+The pwd command returns the absolute path name of the current working directory.
3901+.IP "rename source target"
3902+The rename command renames the file or directory named by the source
3903+operand to the destination path named by the target operand.
3904+.IP "rm file"
3905+The rm command removes the file specified by the file operand.
3906+.IP "rmdir directory"
3907+The rmdir command removes the directory entry specified by the directory
3908+operand, provided it is empty.
3909+.IP "symlink source_file target_file"
3910+See ln.
3911+.RE
3912+.IP
3913+
3914+--quote can be used several times in a command line
3915+
3916+Example:
3917+.nf
3918+ curl --quote "DELE file" ftp://example.com/foo
3919+.fi
3920+
3921+See also \fI-X, \-\-request\fP.
3922+.IP "\-\-random\-file <file>"
3923+Deprecated option. This option is ignored (added in 7.84.0). Prior to that it
3924+only had an effect on curl if built to use old versions of OpenSSL.
3925+
3926+Specify the path name to file containing random data. The data may be used to
3927+seed the random engine for SSL connections.
3928+
3929+If --random-file is provided several times, the last set value is used.
3930+
3931+Example:
3932+.nf
3933+ curl --random-file rubbish https://example.com
3934+.fi
3935+
3936+See also \fI\-\-egd\-file\fP.
3937+.IP "\-r, \-\-range <range>"
3938+(HTTP FTP SFTP FILE) Retrieve a byte range (i.e. a partial document) from an HTTP/1.1, FTP or SFTP
3939+server or a local FILE. Ranges can be specified in a number of ways.
3940+.RS
3941+.IP 0-499
3942+specifies the first 500 bytes
3943+.IP 500-999
3944+specifies the second 500 bytes
3945+.IP -500
3946+specifies the last 500 bytes
3947+.IP 9500-
3948+specifies the bytes from offset 9500 and forward
3949+.IP 0-0,-1
3950+specifies the first and last byte only(*)(HTTP)
3951+.IP 100-199,500-599
3952+specifies two separate 100\-byte ranges(*) (HTTP)
3953+.RE
3954+.IP
3955+(*) = NOTE that these make the server reply with a multipart response, which
3956+is returned as\-is by curl! Parsing or otherwise transforming this response is
3957+the responsibility of the caller.
3958+
3959+Only digit characters (0\-9) are valid in the \(aqstart\(aq and \(aqstop\(aq fields of the
3960+\(aqstart\-stop\(aq range syntax. If a non\-digit character is given in the range, the
3961+server\(aqs response is unspecified, depending on the server\(aqs configuration.
3962+
3963+Many HTTP/1.1 servers do not have this feature enabled, so that when you
3964+attempt to get a range, curl instead gets the whole document.
3965+
3966+FTP and SFTP range downloads only support the simple \(aqstart\-stop\(aq syntax
3967+(optionally with one of the numbers omitted). FTP use depends on the extended
3968+FTP command SIZE.
3969+.RE
3970+.IP
3971+
3972+If --range is provided several times, the last set value is used.
3973+
3974+Example:
3975+.nf
3976+ curl --range 22-44 https://example.com
3977+.fi
3978+
3979+See also \fI-C, \-\-continue\-at\fP and \fI-a, \-\-append\fP.
3980+.IP "\-\-rate <max request rate>"
3981+Specify the maximum transfer frequency you allow curl to use \- in number of
3982+transfer starts per time unit (sometimes called request rate). Without this
3983+option, curl starts the next transfer as fast as possible.
3984+
3985+If given several URLs and a transfer completes faster than the allowed rate,
3986+curl waits until the next transfer is started to maintain the requested
3987+rate. This option has no effect when \fI\-Z, \-\-parallel\fP is used.
3988+
3989+The request rate is provided as "N/U" where N is an integer number and U is a
3990+time unit. Supported units are \(aqs\(aq (second), \(aqm\(aq (minute), \(aqh\(aq (hour) and \(aqd\(aq
3991+/(day, as in a 24 hour unit). The default time unit, if no "/U" is provided,
3992+is number of transfers per hour.
3993+
3994+If curl is told to allow 10 requests per minute, it does not start the next
3995+request until 6 seconds have elapsed since the previous transfer was started.
3996+
3997+This function uses millisecond resolution. If the allowed frequency is set
3998+more than 1000 per second, it instead runs unrestricted.
3999+
4000+When retrying transfers, enabled with \fI\-\-retry\fP, the separate retry delay logic
4001+is used and not this setting.
4002+
4003+This option is global and does not need to be specified for each use of --next.
4004+
4005+If --rate is provided several times, the last set value is used.
4006+
4007+Examples:
4008+.nf
4009+ curl --rate 2/s https://example.com ...
4010+ curl --rate 3/h https://example.com ...
4011+ curl --rate 14/m https://example.com ...
4012+.fi
4013+
4014+See also \fI\-\-limit\-rate\fP and \fI\-\-retry\-delay\fP. Added in 7.84.0.
4015+.IP "\-\-raw"
4016+(HTTP) When used, it disables all internal HTTP decoding of content or transfer
4017+encodings and instead makes them passed on unaltered, raw.
4018+
4019+Providing --raw multiple times has no extra effect.
4020+Disable it again with \-\-no-raw.
4021+
4022+Example:
4023+.nf
4024+ curl --raw https://example.com
4025+.fi
4026+
4027+See also \fI\-\-tr\-encoding\fP.
4028+.IP "\-e, \-\-referer <URL>"
4029+(HTTP) Sends the "Referrer Page" information to the HTTP server. This can also be set
4030+with the \fI\-H, \-\-header\fP flag of course. When used with \fI\-L, \-\-location\fP you can append
4031+\&";auto" to the \fI\-e, \-\-referer\fP URL to make curl automatically set the previous URL
4032+when it follows a Location: header. The ";auto" string can be used alone,
4033+even if you do not set an initial \fI\-e, \-\-referer\fP.
4034+
4035+If --referer is provided several times, the last set value is used.
4036+
4037+Examples:
4038+.nf
4039+ curl --referer "https://fake.example" https://example.com
4040+ curl --referer "https://fake.example;auto" -L https://example.com
4041+ curl --referer ";auto" -L https://example.com
4042+.fi
4043+
4044+See also \fI-A, \-\-user\-agent\fP and \fI-H, \-\-header\fP.
4045+.IP "\-J, \-\-remote\-header\-name"
4046+(HTTP) This option tells the \fI\-O, \-\-remote\-name\fP option to use the server\-specified
4047+Content\-Disposition filename instead of extracting a filename from the URL. If
4048+the server\-provided file name contains a path, that is stripped off before the
4049+file name is used.
4050+
4051+The file is saved in the current directory, or in the directory specified with
4052+\fI\-\-output\-dir\fP.
4053+
4054+If the server specifies a file name and a file with that name already exists
4055+in the destination directory, it is not overwritten and an error occurs \-
4056+unless you allow it by using the \--clobber option. If the server does not
4057+specify a file name then this option has no effect.
4058+
4059+There is no attempt to decode %\-sequences (yet) in the provided file name, so
4060+this option may provide you with rather unexpected file names.
4061+
4062+This feature uses the name from the "filename" field, it does not yet support
4063+the "filename*" field (filenames with explicit character sets).
4064+
4065+\fBWARNING\fP: Exercise judicious use of this option, especially on Windows. A
4066+rogue server could send you the name of a DLL or other file that could be
4067+loaded automatically by Windows or some third party software.
4068+
4069+Providing --remote-header-name multiple times has no extra effect.
4070+Disable it again with \-\-no-remote-header-name.
4071+
4072+Example:
4073+.nf
4074+ curl -OJ https://example.com/file
4075+.fi
4076+
4077+See also \fI-O, \-\-remote\-name\fP.
4078+.IP "\-\-remote\-name\-all"
4079+This option changes the default action for all given URLs to be dealt with as
4080+if \fI\-O, \-\-remote\-name\fP were used for each one. So if you want to disable that for a
4081+specific URL after \fI\-\-remote\-name\-all\fP has been used, you must use "\-o \-" or
4082+-\-no\-remote\-name.
4083+
4084+Providing --remote-name-all multiple times has no extra effect.
4085+Disable it again with \-\-no-remote-name-all.
4086+
4087+Example:
4088+.nf
4089+ curl --remote-name-all ftp://example.com/file1 ftp://example.com/file2
4090+.fi
4091+
4092+See also \fI-O, \-\-remote\-name\fP.
4093+.IP "\-O, \-\-remote\-name"
4094+Write output to a local file named like the remote file we get. (Only the file
4095+part of the remote file is used, the path is cut off.)
4096+
4097+The file is saved in the current working directory. If you want the file saved
4098+in a different directory, make sure you change the current working directory
4099+before invoking curl with this option or use \fI\-\-output\-dir\fP.
4100+
4101+The remote file name to use for saving is extracted from the given URL,
4102+nothing else, and if it already exists it is overwritten. If you want the
4103+server to be able to choose the file name refer to \fI\-J, \-\-remote\-header\-name\fP which
4104+can be used in addition to this option. If the server chooses a file name and
4105+that name already exists it is not overwritten.
4106+
4107+There is no URL decoding done on the file name. If it has %20 or other URL
4108+encoded parts of the name, they end up as\-is as file name.
4109+
4110+You may use this option as many times as the number of URLs you have.
4111+
4112+--remote-name can be used several times in a command line
4113+
4114+Example:
4115+.nf
4116+ curl -O https://example.com/filename
4117+.fi
4118+
4119+See also \fI\-\-remote\-name\-all\fP, \fI\-\-output\-dir\fP and \fI-J, \-\-remote\-header\-name\fP.
4120+.IP "\-R, \-\-remote\-time"
4121+Makes curl attempt to figure out the timestamp of the remote file that is
4122+getting downloaded, and if that is available make the local file get that same
4123+timestamp.
4124+
4125+Providing --remote-time multiple times has no extra effect.
4126+Disable it again with \-\-no-remote-time.
4127+
4128+Example:
4129+.nf
4130+ curl --remote-time -o foo https://example.com
4131+.fi
4132+
4133+See also \fI-O, \-\-remote\-name\fP and \fI-z, \-\-time\-cond\fP.
4134+.IP "\-\-remove\-on\-error"
4135+When curl returns an error when told to save output in a local file, this
4136+option removes that saved file before exiting. This prevents curl from
4137+leaving a partial file in the case of an error during transfer.
4138+
4139+If the output is not a regular file, this option has no effect.
4140+
4141+Providing --remove-on-error multiple times has no extra effect.
4142+Disable it again with \-\-no-remove-on-error.
4143+
4144+Example:
4145+.nf
4146+ curl --remove-on-error -o output https://example.com
4147+.fi
4148+
4149+See also \fI-f, \-\-fail\fP. Added in 7.83.0.
4150+.IP "\-\-request\-target <path>"
4151+(HTTP) Tells curl to use an alternative "target" (path) instead of using the path as
4152+provided in the URL. Particularly useful when wanting to issue HTTP requests
4153+without leading slash or other data that does not follow the regular URL
4154+pattern, like "OPTIONS *".
4155+
4156+curl passes on the verbatim string you give it its the request without any
4157+filter or other safe guards. That includes white space and control characters.
4158+
4159+If --request-target is provided several times, the last set value is used.
4160+
4161+Example:
4162+.nf
4163+ curl --request-target "*" -X OPTIONS https://example.com
4164+.fi
4165+
4166+See also \fI-X, \-\-request\fP. Added in 7.55.0.
4167+.IP "\-X, \-\-request <method>"
4168+Change the method to use when starting the transfer.
4169+
4170+curl passes on the verbatim string you give it its the request without any
4171+filter or other safe guards. That includes white space and control characters.
4172+.RS
4173+.IP HTTP
4174+Specifies a custom request method to use when communicating with the HTTP
4175+server. The specified request method is used instead of the method otherwise
4176+used (which defaults to \fIGET\fP). Read the HTTP 1.1 specification for details
4177+and explanations. Common additional HTTP requests include \fIPUT\fP and \fIDELETE\fP,
4178+while related technologies like WebDAV offers \fIPROPFIND\fP, \fICOPY\fP, \fIMOVE\fP and
4179+more.
4180+
4181+Normally you do not need this option. All sorts of \fIGET\fP, \fIHEAD\fP, \fIPOST\fP and
4182+\fIPUT\fP requests are rather invoked by using dedicated command line options.
4183+
4184+This option only changes the actual word used in the HTTP request, it does not
4185+alter the way curl behaves. So for example if you want to make a proper HEAD
4186+request, using \-X HEAD does not suffice. You need to use the \fI\-I, \-\-head\fP option.
4187+
4188+The method string you set with \fI\-X, \-\-request\fP is used for all requests, which
4189+if you for example use \fI\-L, \-\-location\fP may cause unintended side\-effects when curl
4190+does not change request method according to the HTTP 30x response codes \- and
4191+similar.
4192+.IP FTP
4193+Specifies a custom FTP command to use instead of \fILIST\fP when doing file lists
4194+with FTP.
4195+.IP POP3
4196+Specifies a custom POP3 command to use instead of \fILIST\fP or \fIRETR\fP.
4197+
4198+.IP IMAP
4199+Specifies a custom IMAP command to use instead of \fILIST\fP.
4200+.IP SMTP
4201+Specifies a custom SMTP command to use instead of \fIHELP\fP or \fBVRFY\fP.
4202+.RE
4203+.IP
4204+
4205+If --request is provided several times, the last set value is used.
4206+
4207+Examples:
4208+.nf
4209+ curl -X "DELETE" https://example.com
4210+ curl -X NLST ftp://example.com/
4211+.fi
4212+
4213+See also \fI\-\-request\-target\fP.
4214+.IP "\-\-resolve <[+]host:port:addr[,addr]...>"
4215+Provide a custom address for a specific host and port pair. Using this, you
4216+can make the curl requests(s) use a specified address and prevent the
4217+otherwise normally resolved address to be used. Consider it a sort of
4218+/etc/hosts alternative provided on the command line. The port number should be
4219+the number used for the specific protocol the host is used for. It means
4220+you need several entries if you want to provide address for the same host but
4221+different ports.
4222+
4223+By specifying \(aq*\(aq as host you can tell curl to resolve any host and specific
4224+port pair to the specified address. Wildcard is resolved last so any \fI\-\-resolve\fP
4225+with a specific host and port is used first.
4226+
4227+The provided address set by this option is used even if \fI\-4, \-\-ipv4\fP or \fI\-6, \-\-ipv6\fP is
4228+set to make curl use another IP version.
4229+
4230+By prefixing the host with a \(aq+\(aq you can make the entry time out after curl\(aqs
4231+default timeout (1 minute). Note that this only makes sense for long running
4232+parallel transfers with a lot of files. In such cases, if this option is used
4233+curl tries to resolve the host as it normally would once the timeout has
4234+expired.
4235+
4236+Support for providing the IP address within [brackets] was added in 7.57.0.
4237+
4238+Support for providing multiple IP addresses per entry was added in 7.59.0.
4239+
4240+Support for resolving with wildcard was added in 7.64.0.
4241+
4242+Support for the \(aq+\(aq prefix was was added in 7.75.0.
4243+
4244+--resolve can be used several times in a command line
4245+
4246+Example:
4247+.nf
4248+ curl --resolve example.com:443:127.0.0.1 https://example.com
4249+.fi
4250+
4251+See also \fI\-\-connect\-to\fP and \fI\-\-alt\-svc\fP.
4252+.IP "\-\-retry\-all\-errors"
4253+Retry on any error. This option is used together with \fI\-\-retry\fP.
4254+
4255+This option is the "sledgehammer" of retrying. Do not use this option by
4256+default (for example in your \fBcurlrc\fP), there may be unintended consequences
4257+such as sending or receiving duplicate data. Do not use with redirected input
4258+or output. You\(aqd be much better off handling your unique problems in shell
4259+script. Please read the example below.
4260+
4261+\fBWARNING\fP: For server compatibility curl attempts to retry failed flaky
4262+transfers as close as possible to how they were started, but this is not
4263+possible with redirected input or output. For example, before retrying it
4264+removes output data from a failed partial transfer that was written to an
4265+output file. However this is not true of data redirected to a | pipe or >
4266+file, which are not reset. We strongly suggest you do not parse or record
4267+output via redirect in combination with this option, since you may receive
4268+duplicate data.
4269+
4270+By default curl does not return error for transfers with an HTTP response code
4271+that indicates an HTTP error, if the transfer was successful. For example, if
4272+a server replies 404 Not Found and the reply is fully received then that is
4273+not an error. When \fI\-\-retry\fP is used then curl retries on some HTTP response
4274+codes that indicate transient HTTP errors, but that does not include most 4xx
4275+response codes such as 404. If you want to retry on all response codes that
4276+indicate HTTP errors (4xx and 5xx) then combine with \fI\-f, \-\-fail\fP.
4277+
4278+Providing --retry-all-errors multiple times has no extra effect.
4279+Disable it again with \-\-no-retry-all-errors.
4280+
4281+Example:
4282+.nf
4283+ curl --retry 5 --retry-all-errors https://example.com
4284+.fi
4285+
4286+See also \fI\-\-retry\fP. Added in 7.71.0.
4287+.IP "\-\-retry\-connrefused"
4288+In addition to the other conditions, consider ECONNREFUSED as a transient
4289+error too for \fI\-\-retry\fP. This option is used together with \fI\-\-retry\fP.
4290+
4291+Providing --retry-connrefused multiple times has no extra effect.
4292+Disable it again with \-\-no-retry-connrefused.
4293+
4294+Example:
4295+.nf
4296+ curl --retry-connrefused --retry 7 https://example.com
4297+.fi
4298+
4299+See also \fI\-\-retry\fP and \fI\-\-retry\-all\-errors\fP. Added in 7.52.0.
4300+.IP "\-\-retry\-delay <seconds>"
4301+Make curl sleep this amount of time before each retry when a transfer has
4302+failed with a transient error (it changes the default backoff time algorithm
4303+between retries). This option is only interesting if \fI\-\-retry\fP is also
4304+used. Setting this delay to zero makes curl use the default backoff time.
4305+
4306+If --retry-delay is provided several times, the last set value is used.
4307+
4308+Example:
4309+.nf
4310+ curl --retry-delay 5 --retry 7 https://example.com
4311+.fi
4312+
4313+See also \fI\-\-retry\fP.
4314+.IP "\-\-retry\-max\-time <seconds>"
4315+The retry timer is reset before the first transfer attempt. Retries are done
4316+as usual (see \fI\-\-retry\fP) as long as the timer has not reached this given
4317+limit. Notice that if the timer has not reached the limit, the request is
4318+made and while performing, it may take longer than this given time period. To
4319+limit a single request\(aqs maximum time, use \fI\-m, \-\-max\-time\fP. Set this option to zero
4320+to not timeout retries.
4321+
4322+If --retry-max-time is provided several times, the last set value is used.
4323+
4324+Example:
4325+.nf
4326+ curl --retry-max-time 30 --retry 10 https://example.com
4327+.fi
4328+
4329+See also \fI\-\-retry\fP.
4330+.IP "\-\-retry <num>"
4331+If a transient error is returned when curl tries to perform a transfer, it
4332+retries this number of times before giving up. Setting the number to 0
4333+makes curl do no retries (which is the default). Transient error means either:
4334+a timeout, an FTP 4xx response code or an HTTP 408, 429, 500, 502, 503 or 504
4335+response code.
4336+
4337+When curl is about to retry a transfer, it first waits one second and then for
4338+all forthcoming retries it doubles the waiting time until it reaches 10
4339+minutes which then remains delay between the rest of the retries. By using
4340+\fI\-\-retry\-delay\fP you disable this exponential backoff algorithm. See also
4341+\fI\-\-retry\-max\-time\fP to limit the total time allowed for retries.
4342+
4343+curl complies with the Retry\-After: response header if one was present to know
4344+when to issue the next retry (added in 7.66.0).
4345+
4346+If --retry is provided several times, the last set value is used.
4347+
4348+Example:
4349+.nf
4350+ curl --retry 7 https://example.com
4351+.fi
4352+
4353+See also \fI\-\-retry\-max\-time\fP.
4354+.IP "\-\-sasl\-authzid <identity>"
4355+Use this authorization identity (\fBauthzid\fP), during SASL PLAIN
4356+authentication, in addition to the authentication identity (\fBauthcid\fP) as
4357+specified by \fI\-u, \-\-user\fP.
4358+
4359+If the option is not specified, the server derives the \fBauthzid\fP from the
4360+\fBauthcid\fP, but if specified, and depending on the server implementation, it
4361+may be used to access another user\(aqs inbox, that the user has been granted
4362+access to, or a shared mailbox for example.
4363+
4364+If --sasl-authzid is provided several times, the last set value is used.
4365+
4366+Example:
4367+.nf
4368+ curl --sasl-authzid zid imap://example.com/
4369+.fi
4370+
4371+See also \fI\-\-login\-options\fP. Added in 7.66.0.
4372+.IP "\-\-sasl\-ir"
4373+Enable initial response in SASL authentication.
4374+
4375+Providing --sasl-ir multiple times has no extra effect.
4376+Disable it again with \-\-no-sasl-ir.
4377+
4378+Example:
4379+.nf
4380+ curl --sasl-ir imap://example.com/
4381+.fi
4382+
4383+See also \fI\-\-sasl\-authzid\fP.
4384+.IP "\-\-service\-name <name>"
4385+This option allows you to change the service name for SPNEGO.
4386+
4387+If --service-name is provided several times, the last set value is used.
4388+
4389+Example:
4390+.nf
4391+ curl --service-name sockd/server https://example.com
4392+.fi
4393+
4394+See also \fI\-\-negotiate\fP and \fI\-\-proxy\-service\-name\fP.
4395+.IP "\-S, \-\-show\-error"
4396+When used with \fI\-s, \-\-silent\fP, it makes curl show an error message if it fails.
4397+
4398+This option is global and does not need to be specified for each use of --next.
4399+
4400+Providing --show-error multiple times has no extra effect.
4401+Disable it again with \-\-no-show-error.
4402+
4403+Example:
4404+.nf
4405+ curl --show-error --silent https://example.com
4406+.fi
4407+
4408+See also \fI\-\-no\-progress\-meter\fP.
4409+.IP "\-s, \-\-silent"
4410+Silent or quiet mode. Do not show progress meter or error messages. Makes Curl
4411+mute. It still outputs the data you ask for, potentially even to the
4412+terminal/stdout unless you redirect it.
4413+
4414+Use \fI\-S, \-\-show\-error\fP in addition to this option to disable progress meter but
4415+still show error messages.
4416+
4417+Providing --silent multiple times has no extra effect.
4418+Disable it again with \-\-no-silent.
4419+
4420+Example:
4421+.nf
4422+ curl -s https://example.com
4423+.fi
4424+
4425+See also \fI-v, \-\-verbose\fP, \fI\-\-stderr\fP and \fI\-\-no\-progress\-meter\fP.
4426+.IP "\-\-socks4 <host[:port]>"
4427+Use the specified SOCKS4 proxy. If the port number is not specified, it is
4428+assumed at port 1080. Using this socket type make curl resolve the host name
4429+and passing the address on to the proxy.
4430+
4431+To specify proxy on a unix domain socket, use localhost for host, e.g.
4432+\&"socks4://localhost/path/to/socket.sock"
4433+
4434+This option overrides any previous use of \fI\-x, \-\-proxy\fP, as they are mutually
4435+exclusive.
4436+
4437+This option is superfluous since you can specify a socks4 proxy with \fI\-x, \-\-proxy\fP
4438+using a socks4:// protocol prefix.
4439+
4440+\fI\-\-preproxy\fP can be used to specify a SOCKS proxy at the same time proxy is used
4441+with an HTTP/HTTPS proxy (added in 7.52.0). In such a case, curl first
4442+connects to the SOCKS proxy and then connects (through SOCKS) to the HTTP or
4443+HTTPS proxy.
4444+
4445+If --socks4 is provided several times, the last set value is used.
4446+
4447+Example:
4448+.nf
4449+ curl --socks4 hostname:4096 https://example.com
4450+.fi
4451+
4452+See also \fI\-\-socks4a\fP, \fI\-\-socks5\fP and \fI\-\-socks5\-hostname\fP.
4453+.IP "\-\-socks4a <host[:port]>"
4454+Use the specified SOCKS4a proxy. If the port number is not specified, it is
4455+assumed at port 1080. This asks the proxy to resolve the host name.
4456+
4457+To specify proxy on a unix domain socket, use localhost for host, e.g.
4458+\&"socks4a://localhost/path/to/socket.sock"
4459+
4460+This option overrides any previous use of \fI\-x, \-\-proxy\fP, as they are mutually
4461+exclusive.
4462+
4463+This option is superfluous since you can specify a socks4a proxy with \fI\-x, \-\-proxy\fP
4464+using a socks4a:// protocol prefix.
4465+
4466+\fI\-\-preproxy\fP can be used to specify a SOCKS proxy at the same time \fI\-x, \-\-proxy\fP is
4467+used with an HTTP/HTTPS proxy (added in 7.52.0). In such a case, curl first
4468+connects to the SOCKS proxy and then connects (through SOCKS) to the HTTP or
4469+HTTPS proxy.
4470+
4471+If --socks4a is provided several times, the last set value is used.
4472+
4473+Example:
4474+.nf
4475+ curl --socks4a hostname:4096 https://example.com
4476+.fi
4477+
4478+See also \fI\-\-socks4\fP, \fI\-\-socks5\fP and \fI\-\-socks5\-hostname\fP.
4479+.IP "\-\-socks5\-basic"
4480+Tells curl to use username/password authentication when connecting to a SOCKS5
4481+proxy. The username/password authentication is enabled by default. Use
4482+\fI\-\-socks5\-gssapi\fP to force GSS\-API authentication to SOCKS5 proxies.
4483+
4484+Providing --socks5-basic multiple times has no extra effect.
4485+
4486+Example:
4487+.nf
4488+ curl --socks5-basic --socks5 hostname:4096 https://example.com
4489+.fi
4490+
4491+See also \fI\-\-socks5\fP. Added in 7.55.0.
4492+.IP "\-\-socks5\-gssapi\-nec"
4493+As part of the GSS\-API negotiation a protection mode is negotiated. RFC 1961
4494+says in section 4.3/4.4 it should be protected, but the NEC reference
4495+implementation does not. The option \fI\-\-socks5\-gssapi\-nec\fP allows the
4496+unprotected exchange of the protection mode negotiation.
4497+
4498+Providing --socks5-gssapi-nec multiple times has no extra effect.
4499+Disable it again with \-\-no-socks5-gssapi-nec.
4500+
4501+Example:
4502+.nf
4503+ curl --socks5-gssapi-nec --socks5 hostname:4096 https://example.com
4504+.fi
4505+
4506+See also \fI\-\-socks5\fP.
4507+.IP "\-\-socks5\-gssapi\-service <name>"
4508+The default service name for a socks server is \fBrcmd/server\-fqdn\fP. This option
4509+allows you to change it.
4510+
4511+If --socks5-gssapi-service is provided several times, the last set value is used.
4512+
4513+Example:
4514+.nf
4515+ curl --socks5-gssapi-service sockd --socks5 hostname:4096 https://example.com
4516+.fi
4517+
4518+See also \fI\-\-socks5\fP.
4519+.IP "\-\-socks5\-gssapi"
4520+Tells curl to use GSS\-API authentication when connecting to a SOCKS5 proxy.
4521+The GSS\-API authentication is enabled by default (if curl is compiled with
4522+GSS\-API support). Use \fI\-\-socks5\-basic\fP to force username/password authentication
4523+to SOCKS5 proxies.
4524+
4525+Providing --socks5-gssapi multiple times has no extra effect.
4526+Disable it again with \-\-no-socks5-gssapi.
4527+
4528+Example:
4529+.nf
4530+ curl --socks5-gssapi --socks5 hostname:4096 https://example.com
4531+.fi
4532+
4533+See also \fI\-\-socks5\fP. Added in 7.55.0.
4534+.IP "\-\-socks5\-hostname <host[:port]>"
4535+Use the specified SOCKS5 proxy (and let the proxy resolve the host name). If
4536+the port number is not specified, it is assumed at port 1080.
4537+
4538+To specify proxy on a unix domain socket, use localhost for host, e.g.
4539+\&"socks5h://localhost/path/to/socket.sock"
4540+
4541+This option overrides any previous use of \fI\-x, \-\-proxy\fP, as they are mutually
4542+exclusive.
4543+
4544+This option is superfluous since you can specify a socks5 hostname proxy with
4545+\fI\-x, \-\-proxy\fP using a socks5h:// protocol prefix.
4546+
4547+\fI\-\-preproxy\fP can be used to specify a SOCKS proxy at the same time \fI\-x, \-\-proxy\fP is
4548+used with an HTTP/HTTPS proxy (added in 7.52.0). In such a case, curl first
4549+connects to the SOCKS proxy and then connects (through SOCKS) to the HTTP or
4550+HTTPS proxy.
4551+
4552+If --socks5-hostname is provided several times, the last set value is used.
4553+
4554+Example:
4555+.nf
4556+ curl --socks5-hostname proxy.example:7000 https://example.com
4557+.fi
4558+
4559+See also \fI\-\-socks5\fP and \fI\-\-socks4a\fP.
4560+.IP "\-\-socks5 <host[:port]>"
4561+Use the specified SOCKS5 proxy \- but resolve the host name locally. If the
4562+port number is not specified, it is assumed at port 1080.
4563+
4564+To specify proxy on a unix domain socket, use localhost for host, e.g.
4565+\&"socks5://localhost/path/to/socket.sock"
4566+
4567+This option overrides any previous use of \fI\-x, \-\-proxy\fP, as they are mutually
4568+exclusive.
4569+
4570+This option is superfluous since you can specify a socks5 proxy with \fI\-x, \-\-proxy\fP
4571+using a socks5:// protocol prefix.
4572+
4573+\fI\-\-preproxy\fP can be used to specify a SOCKS proxy at the same time \fI\-x, \-\-proxy\fP is
4574+used with an HTTP/HTTPS proxy (added in 7.52.0). In such a case, curl first
4575+connects to the SOCKS proxy and then connects (through SOCKS) to the HTTP or
4576+HTTPS proxy.
4577+
4578+This option (as well as \fI\-\-socks4\fP) does not work with IPV6, FTPS or LDAP.
4579+
4580+If --socks5 is provided several times, the last set value is used.
4581+
4582+Example:
4583+.nf
4584+ curl --socks5 proxy.example:7000 https://example.com
4585+.fi
4586+
4587+See also \fI\-\-socks5\-hostname\fP and \fI\-\-socks4a\fP.
4588+.IP "\-Y, \-\-speed\-limit <speed>"
4589+If a transfer is slower than this set speed (in bytes per second) for a given
4590+number of seconds, it gets aborted. The time period is set with \fI\-y, \-\-speed\-time\fP
4591+and is 30 seconds by default.
4592+
4593+If --speed-limit is provided several times, the last set value is used.
4594+
4595+Example:
4596+.nf
4597+ curl --speed-limit 300 --speed-time 10 https://example.com
4598+.fi
4599+
4600+See also \fI-y, \-\-speed\-time\fP, \fI\-\-limit\-rate\fP and \fI-m, \-\-max\-time\fP.
4601+.IP "\-y, \-\-speed\-time <seconds>"
4602+If a transfer runs slower than speed\-limit bytes per second during a
4603+speed\-time period, the transfer is aborted. If speed\-time is used, the default
4604+speed\-limit is 1 unless set with \fI\-Y, \-\-speed\-limit\fP.
4605+
4606+This option controls transfers (in both directions) but does not affect slow
4607+connects etc. If this is a concern for you, try the \fI\-\-connect\-timeout\fP option.
4608+
4609+If --speed-time is provided several times, the last set value is used.
4610+
4611+Example:
4612+.nf
4613+ curl --speed-limit 300 --speed-time 10 https://example.com
4614+.fi
4615+
4616+See also \fI-Y, \-\-speed\-limit\fP and \fI\-\-limit\-rate\fP.
4617+.IP "\-\-ssl\-allow\-beast"
4618+(TLS) This option tells curl to not work around a security flaw in the SSL3 and
4619+TLS1.0 protocols known as BEAST. If this option is not used, the SSL layer may
4620+use workarounds known to cause interoperability problems with some older SSL
4621+implementations.
4622+
4623+\fBWARNING\fP: this option loosens the SSL security, and by using this flag you
4624+ask for exactly that.
4625+
4626+Providing --ssl-allow-beast multiple times has no extra effect.
4627+Disable it again with \-\-no-ssl-allow-beast.
4628+
4629+Example:
4630+.nf
4631+ curl --ssl-allow-beast https://example.com
4632+.fi
4633+
4634+See also \fI\-\-proxy\-ssl\-allow\-beast\fP and \fI-k, \-\-insecure\fP.
4635+.IP "\-\-ssl\-auto\-client\-cert"
4636+(TLS) (Schannel) Tell libcurl to automatically locate and use a client certificate
4637+for authentication, when requested by the server. Since the server can request
4638+any certificate that supports client authentication in the OS certificate
4639+store it could be a privacy violation and unexpected.
4640+
4641+Providing --ssl-auto-client-cert multiple times has no extra effect.
4642+Disable it again with \-\-no-ssl-auto-client-cert.
4643+
4644+Example:
4645+.nf
4646+ curl --ssl-auto-client-cert https://example.com
4647+.fi
4648+
4649+See also \fI\-\-proxy\-ssl\-auto\-client\-cert\fP. Added in 7.77.0.
4650+.IP "\-\-ssl\-no\-revoke"
4651+(TLS) (Schannel) This option tells curl to disable certificate revocation checks.
4652+WARNING: this option loosens the SSL security, and by using this flag you ask
4653+for exactly that.
4654+
4655+Providing --ssl-no-revoke multiple times has no extra effect.
4656+Disable it again with \-\-no-ssl-no-revoke.
4657+
4658+Example:
4659+.nf
4660+ curl --ssl-no-revoke https://example.com
4661+.fi
4662+
4663+See also \fI\-\-crlfile\fP.
4664+.IP "\-\-ssl\-reqd"
4665+(FTP IMAP POP3 SMTP LDAP) Require SSL/TLS for the connection. Terminates the connection if the transfer
4666+cannot be upgraded to use SSL/TLS.
4667+
4668+This option is handled in LDAP (added in 7.81.0). It is fully supported by the
4669+OpenLDAP backend and rejected by the generic ldap backend if explicit TLS is
4670+required.
4671+
4672+This option is unnecessary if you use a URL scheme that in itself implies
4673+immediate and implicit use of TLS, like for FTPS, IMAPS, POP3S, SMTPS and
4674+LDAPS. Such a transfer always fails if the TLS handshake does not work.
4675+
4676+This option was formerly known as \--ftp\-ssl\-reqd.
4677+
4678+Providing --ssl-reqd multiple times has no extra effect.
4679+Disable it again with \-\-no-ssl-reqd.
4680+
4681+Example:
4682+.nf
4683+ curl --ssl-reqd ftp://example.com
4684+.fi
4685+
4686+See also \fI\-\-ssl\fP and \fI-k, \-\-insecure\fP.
4687+.IP "\-\-ssl\-revoke\-best\-effort"
4688+(TLS) (Schannel) This option tells curl to ignore certificate revocation checks when
4689+they failed due to missing/offline distribution points for the revocation check
4690+lists.
4691+
4692+Providing --ssl-revoke-best-effort multiple times has no extra effect.
4693+Disable it again with \-\-no-ssl-revoke-best-effort.
4694+
4695+Example:
4696+.nf
4697+ curl --ssl-revoke-best-effort https://example.com
4698+.fi
4699+
4700+See also \fI\-\-crlfile\fP and \fI-k, \-\-insecure\fP. Added in 7.70.0.
4701+.IP "\-\-ssl"
4702+(FTP IMAP POP3 SMTP LDAP) Warning: this is considered an insecure option. Consider using \fI\-\-ssl\-reqd\fP
4703+instead to be sure curl upgrades to a secure connection.
4704+
4705+Try to use SSL/TLS for the connection. Reverts to a non\-secure connection if
4706+the server does not support SSL/TLS. See also \fI\-\-ftp\-ssl\-control\fP and \fI\-\-ssl\-reqd\fP
4707+for different levels of encryption required.
4708+
4709+This option is handled in LDAP (added in 7.81.0). It is fully supported by the
4710+OpenLDAP backend and ignored by the generic ldap backend.
4711+
4712+Please note that a server may close the connection if the negotiation does
4713+not succeed.
4714+
4715+This option was formerly known as \--ftp\-ssl. That option
4716+name can still be used but might be removed in a future version.
4717+
4718+Providing --ssl multiple times has no extra effect.
4719+Disable it again with \-\-no-ssl.
4720+
4721+Example:
4722+.nf
4723+ curl --ssl pop3://example.com/
4724+.fi
4725+
4726+See also \fI\-\-ssl\-reqd\fP, \fI-k, \-\-insecure\fP and \fI\-\-ciphers\fP.
4727+.IP "\-2, \-\-sslv2"
4728+(SSL) This option previously asked curl to use SSLv2, but is now ignored
4729+(added in 7.77.0). SSLv2 is widely considered insecure (see RFC 6176).
4730+
4731+Providing --sslv2 multiple times has no extra effect.
4732+
4733+Example:
4734+.nf
4735+ curl --sslv2 https://example.com
4736+.fi
4737+
4738+See also \fI\-\-http1.1\fP and \fI\-\-http2\fP. \fI-2, \-\-sslv2\fP requires that the underlying libcurl was built to support TLS. This option is mutually exclusive to \fI-3, \-\-sslv3\fP and \fI-1, \-\-tlsv1\fP and \fI\-\-tlsv1.1\fP and \fI\-\-tlsv1.2\fP.
4739+.IP "\-3, \-\-sslv3"
4740+(SSL) This option previously asked curl to use SSLv3, but is now ignored
4741+(added in 7.77.0). SSLv3 is widely considered insecure (see RFC 7568).
4742+
4743+Providing --sslv3 multiple times has no extra effect.
4744+
4745+Example:
4746+.nf
4747+ curl --sslv3 https://example.com
4748+.fi
4749+
4750+See also \fI\-\-http1.1\fP and \fI\-\-http2\fP. \fI-3, \-\-sslv3\fP requires that the underlying libcurl was built to support TLS. This option is mutually exclusive to \fI-2, \-\-sslv2\fP and \fI-1, \-\-tlsv1\fP and \fI\-\-tlsv1.1\fP and \fI\-\-tlsv1.2\fP.
4751+.IP "\-\-stderr <file>"
4752+Redirect all writes to stderr to the specified file instead. If the file name
4753+is a plain \(aq\-\(aq, it is instead written to stdout.
4754+
4755+This option is global and does not need to be specified for each use of --next.
4756+
4757+If --stderr is provided several times, the last set value is used.
4758+
4759+Example:
4760+.nf
4761+ curl --stderr output.txt https://example.com
4762+.fi
4763+
4764+See also \fI-v, \-\-verbose\fP and \fI-s, \-\-silent\fP.
4765+.IP "\-\-styled\-output"
4766+Enables the automatic use of bold font styles when writing HTTP headers to the
4767+terminal. Use \--no\-styled\-output to switch them off.
4768+
4769+Styled output requires a terminal that supports bold fonts. This feature is
4770+not present on curl for Windows due to lack of this capability.
4771+
4772+This option is global and does not need to be specified for each use of --next.
4773+
4774+Providing --styled-output multiple times has no extra effect.
4775+Disable it again with \-\-no-styled-output.
4776+
4777+Example:
4778+.nf
4779+ curl --styled-output -I https://example.com
4780+.fi
4781+
4782+See also \fI-I, \-\-head\fP and \fI-v, \-\-verbose\fP. Added in 7.61.0.
4783+.IP "\-\-suppress\-connect\-headers"
4784+When \fI\-p, \-\-proxytunnel\fP is used and a CONNECT request is made do not output proxy
4785+CONNECT response headers. This option is meant to be used with \fI\-D, \-\-dump\-header\fP or
4786+\fI\-i, \-\-include\fP which are used to show protocol headers in the output. It has no
4787+effect on debug options such as \fI\-v, \-\-verbose\fP or \fI\-\-trace\fP, or any statistics.
4788+
4789+Providing --suppress-connect-headers multiple times has no extra effect.
4790+Disable it again with \-\-no-suppress-connect-headers.
4791+
4792+Example:
4793+.nf
4794+ curl --suppress-connect-headers --include -x proxy https://example.com
4795+.fi
4796+
4797+See also \fI-D, \-\-dump\-header\fP, \fI-i, \-\-include\fP and \fI-p, \-\-proxytunnel\fP. Added in 7.54.0.
4798+.IP "\-\-tcp\-fastopen"
4799+Enable use of TCP Fast Open (RFC 7413). TCP Fast Open is a TCP extension that
4800+allows data to get sent earlier over the connection (before the final
4801+handshake ACK) if the client and server have been connected previously.
4802+
4803+Providing --tcp-fastopen multiple times has no extra effect.
4804+Disable it again with \-\-no-tcp-fastopen.
4805+
4806+Example:
4807+.nf
4808+ curl --tcp-fastopen https://example.com
4809+.fi
4810+
4811+See also \fI\-\-false\-start\fP.
4812+.IP "\-\-tcp\-nodelay"
4813+Turn on the TCP_NODELAY option. See the \fIcurl_easy_setopt(3)\fP man page for
4814+details about this option.
4815+
4816+curl sets this option by default and you need to explicitly switch it off if
4817+you do not want it on (added in 7.50.2).
4818+
4819+Providing --tcp-nodelay multiple times has no extra effect.
4820+Disable it again with \-\-no-tcp-nodelay.
4821+
4822+Example:
4823+.nf
4824+ curl --tcp-nodelay https://example.com
4825+.fi
4826+
4827+See also \fI-N, \-\-no\-buffer\fP.
4828+.IP "\-t, \-\-telnet\-option <opt=val>"
4829+Pass options to the telnet protocol. Supported options are:
4830+.RS
4831+.IP `TTYPE=<term>`
4832+Sets the terminal type.
4833+.IP "`XDISPLOC=<X display>`"
4834+Sets the X display location.
4835+.IP `NEW_ENV=<var,val>`
4836+Sets an environment variable.
4837+.RE
4838+.IP
4839+
4840+--telnet-option can be used several times in a command line
4841+
4842+Example:
4843+.nf
4844+ curl -t TTYPE=vt100 telnet://example.com/
4845+.fi
4846+
4847+See also \fI-K, \-\-config\fP.
4848+.IP "\-\-tftp\-blksize <value>"
4849+(TFTP) Set the TFTP \fBBLKSIZE\fP option (must be >512). This is the block size that
4850+curl tries to use when transferring data to or from a TFTP server. By
4851+default 512 bytes are used.
4852+
4853+If --tftp-blksize is provided several times, the last set value is used.
4854+
4855+Example:
4856+.nf
4857+ curl --tftp-blksize 1024 tftp://example.com/file
4858+.fi
4859+
4860+See also \fI\-\-tftp\-no\-options\fP.
4861+.IP "\-\-tftp\-no\-options"
4862+(TFTP) Tells curl not to send TFTP options requests.
4863+
4864+This option improves interop with some legacy servers that do not acknowledge
4865+or properly implement TFTP options. When this option is used \fI\-\-tftp\-blksize\fP is
4866+ignored.
4867+
4868+Providing --tftp-no-options multiple times has no extra effect.
4869+Disable it again with \-\-no-tftp-no-options.
4870+
4871+Example:
4872+.nf
4873+ curl --tftp-no-options tftp://192.168.0.1/
4874+.fi
4875+
4876+See also \fI\-\-tftp\-blksize\fP.
4877+.IP "\-z, \-\-time\-cond <time>"
4878+(HTTP FTP) Request a file that has been modified later than the given time and date, or
4879+one that has been modified before that time. The <date expression> can be all
4880+sorts of date strings or if it does not match any internal ones, it is taken as
4881+a filename and tries to get the modification date (mtime) from <file>
4882+instead. See the \fIcurl_getdate(3)\fP man pages for date expression details.
4883+
4884+Start the date expression with a dash (\-) to make it request for a document
4885+that is older than the given date/time, default is a document that is newer
4886+than the specified date/time.
4887+
4888+If provided a non\-existing file, curl outputs a warning about that fact and
4889+proceeds to do the transfer without a time condition.
4890+
4891+If --time-cond is provided several times, the last set value is used.
4892+
4893+Examples:
4894+.nf
4895+ curl -z "Wed 01 Sep 2021 12:18:00" https://example.com
4896+ curl -z "-Wed 01 Sep 2021 12:18:00" https://example.com
4897+ curl -z file https://example.com
4898+.fi
4899+
4900+See also \fI\-\-etag\-compare\fP and \fI-R, \-\-remote\-time\fP.
4901+.IP "\-\-tls\-max <VERSION>"
4902+(TLS) VERSION defines maximum supported TLS version. The minimum acceptable version
4903+is set by tlsv1.0, tlsv1.1, tlsv1.2 or tlsv1.3.
4904+
4905+If the connection is done without TLS, this option has no effect. This
4906+includes QUIC\-using (HTTP/3) transfers.
4907+.RS
4908+.IP default
4909+Use up to recommended TLS version.
4910+.IP 1.0
4911+Use up to TLSv1.0.
4912+.IP 1.1
4913+Use up to TLSv1.1.
4914+.IP 1.2
4915+Use up to TLSv1.2.
4916+.IP 1.3
4917+Use up to TLSv1.3.
4918+.RE
4919+.IP
4920+
4921+If --tls-max is provided several times, the last set value is used.
4922+
4923+Examples:
4924+.nf
4925+ curl --tls-max 1.2 https://example.com
4926+ curl --tls-max 1.3 --tlsv1.2 https://example.com
4927+.fi
4928+
4929+See also \fI\-\-tlsv1.0\fP, \fI\-\-tlsv1.1\fP, \fI\-\-tlsv1.2\fP and \fI\-\-tlsv1.3\fP. \fI\-\-tls\-max\fP requires that the underlying libcurl was built to support TLS. Added in 7.54.0.
4930+.IP "\-\-tls13\-ciphers <ciphersuite list>"
4931+(TLS) Specifies which cipher suites to use in the connection if it negotiates TLS
4932+1.3. The list of ciphers suites must specify valid ciphers. Read up on TLS 1.3
4933+cipher suite details on this URL:
4934+
4935+https://curl.se/docs/ssl\-ciphers.html
4936+
4937+This option is currently used only when curl is built to use OpenSSL 1.1.1 or
4938+later, or Schannel. If you are using a different SSL backend you can try
4939+setting TLS 1.3 cipher suites by using the \fI\-\-ciphers\fP option.
4940+
4941+If --tls13-ciphers is provided several times, the last set value is used.
4942+
4943+Example:
4944+.nf
4945+ curl --tls13-ciphers TLS_AES_128_GCM_SHA256 https://example.com
4946+.fi
4947+
4948+See also \fI\-\-ciphers\fP, \fI\-\-curves\fP and \fI\-\-proxy\-tls13\-ciphers\fP. Added in 7.61.0.
4949+.IP "\-\-tlsauthtype <type>"
4950+(TLS) Set TLS authentication type. Currently, the only supported option is "SRP",
4951+for TLS\-SRP (RFC 5054). If \fI\-\-tlsuser\fP and \fI\-\-tlspassword\fP are specified but
4952+\fI\-\-tlsauthtype\fP is not, then this option defaults to "SRP". This option works
4953+only if the underlying libcurl is built with TLS\-SRP support, which requires
4954+OpenSSL or GnuTLS with TLS\-SRP support.
4955+
4956+If --tlsauthtype is provided several times, the last set value is used.
4957+
4958+Example:
4959+.nf
4960+ curl --tlsauthtype SRP https://example.com
4961+.fi
4962+
4963+See also \fI\-\-tlsuser\fP.
4964+.IP "\-\-tlspassword <string>"
4965+(TLS) Set password for use with the TLS authentication method specified with
4966+\fI\-\-tlsauthtype\fP. Requires that \fI\-\-tlsuser\fP also be set.
4967+
4968+This option does not work with TLS 1.3.
4969+
4970+If --tlspassword is provided several times, the last set value is used.
4971+
4972+Example:
4973+.nf
4974+ curl --tlspassword pwd --tlsuser user https://example.com
4975+.fi
4976+
4977+See also \fI\-\-tlsuser\fP.
4978+.IP "\-\-tlsuser <name>"
4979+(TLS) Set username for use with the TLS authentication method specified with
4980+\fI\-\-tlsauthtype\fP. Requires that \fI\-\-tlspassword\fP also is set.
4981+
4982+This option does not work with TLS 1.3.
4983+
4984+If --tlsuser is provided several times, the last set value is used.
4985+
4986+Example:
4987+.nf
4988+ curl --tlspassword pwd --tlsuser user https://example.com
4989+.fi
4990+
4991+See also \fI\-\-tlspassword\fP.
4992+.IP "\-\-tlsv1.0"
4993+(TLS) Forces curl to use TLS version 1.0 or later when connecting to a remote TLS server.
4994+
4995+In old versions of curl this option was documented to allow _only_ TLS 1.0.
4996+That behavior was inconsistent depending on the TLS library. Use \fI\-\-tls\-max\fP if
4997+you want to set a maximum TLS version.
4998+
4999+Providing --tlsv1.0 multiple times has no extra effect.
5000+
5001+Example:
5002+.nf
5003+ curl --tlsv1.0 https://example.com
5004+.fi
5005+
5006+See also \fI\-\-tlsv1.3\fP.
5007+.IP "\-\-tlsv1.1"
5008+(TLS) Forces curl to use TLS version 1.1 or later when connecting to a remote TLS server.
5009+
5010+In old versions of curl this option was documented to allow _only_ TLS 1.1.
5011+That behavior was inconsistent depending on the TLS library. Use \fI\-\-tls\-max\fP if
5012+you want to set a maximum TLS version.
5013+
5014+Providing --tlsv1.1 multiple times has no extra effect.
5015+
5016+Example:
5017+.nf
5018+ curl --tlsv1.1 https://example.com
5019+.fi
5020+
5021+See also \fI\-\-tlsv1.3\fP and \fI\-\-tls\-max\fP.
5022+.IP "\-\-tlsv1.2"
5023+(TLS) Forces curl to use TLS version 1.2 or later when connecting to a remote TLS server.
5024+
5025+In old versions of curl this option was documented to allow _only_ TLS 1.2.
5026+That behavior was inconsistent depending on the TLS library. Use \fI\-\-tls\-max\fP if
5027+you want to set a maximum TLS version.
5028+
5029+Providing --tlsv1.2 multiple times has no extra effect.
5030+
5031+Example:
5032+.nf
5033+ curl --tlsv1.2 https://example.com
5034+.fi
5035+
5036+See also \fI\-\-tlsv1.3\fP and \fI\-\-tls\-max\fP.
5037+.IP "\-\-tlsv1.3"
5038+(TLS) Forces curl to use TLS version 1.3 or later when connecting to a remote TLS
5039+server.
5040+
5041+If the connection is done without TLS, this option has no effect. This
5042+includes QUIC\-using (HTTP/3) transfers.
5043+
5044+Note that TLS 1.3 is not supported by all TLS backends.
5045+
5046+Providing --tlsv1.3 multiple times has no extra effect.
5047+
5048+Example:
5049+.nf
5050+ curl --tlsv1.3 https://example.com
5051+.fi
5052+
5053+See also \fI\-\-tlsv1.2\fP and \fI\-\-tls\-max\fP. Added in 7.52.0.
5054+.IP "\-1, \-\-tlsv1"
5055+(TLS) Tells curl to use at least TLS version 1.x when negotiating with a remote TLS
5056+server. That means TLS version 1.0 or higher
5057+
5058+Providing --tlsv1 multiple times has no extra effect.
5059+
5060+Example:
5061+.nf
5062+ curl --tlsv1 https://example.com
5063+.fi
5064+
5065+See also \fI\-\-http1.1\fP and \fI\-\-http2\fP. \fI-1, \-\-tlsv1\fP requires that the underlying libcurl was built to support TLS. This option is mutually exclusive to \fI\-\-tlsv1.1\fP and \fI\-\-tlsv1.2\fP and \fI\-\-tlsv1.3\fP.
5066+.IP "\-\-tr\-encoding"
5067+(HTTP) Request a compressed Transfer\-Encoding response using one of the algorithms
5068+curl supports, and uncompress the data while receiving it.
5069+
5070+Providing --tr-encoding multiple times has no extra effect.
5071+Disable it again with \-\-no-tr-encoding.
5072+
5073+Example:
5074+.nf
5075+ curl --tr-encoding https://example.com
5076+.fi
5077+
5078+See also \fI\-\-compressed\fP.
5079+.IP "\-\-trace\-ascii <file>"
5080+Enables a full trace dump of all incoming and outgoing data, including
5081+descriptive information, to the given output file. Use "\-" as filename to have
5082+the output sent to stdout.
5083+
5084+This is similar to \fI\-\-trace\fP, but leaves out the hex part and only shows the
5085+ASCII part of the dump. It makes smaller output that might be easier to read
5086+for untrained humans.
5087+
5088+Note that verbose output of curl activities and network traffic might contain
5089+sensitive data, including user names, credentials or secret data content. Be
5090+aware and be careful when sharing trace logs with others.
5091+
5092+This option is global and does not need to be specified for each use of --next.
5093+
5094+If --trace-ascii is provided several times, the last set value is used.
5095+
5096+Example:
5097+.nf
5098+ curl --trace-ascii log.txt https://example.com
5099+.fi
5100+
5101+See also \fI-v, \-\-verbose\fP and \fI\-\-trace\fP. This option is mutually exclusive to \fI\-\-trace\fP and \fI-v, \-\-verbose\fP.
5102+.IP "\-\-trace\-config <string>"
5103+Set configuration for trace output. A comma\-separated list of components where
5104+detailed output can be made available from. Names are case\-insensitive.
5105+Specify \(aqall\(aq to enable all trace components.
5106+
5107+In addition to trace component names, specify "ids" and "time" to
5108+avoid extra \fI\-\-trace\-ids\fP or \fI\-\-trace\-time\fP parameters.
5109+
5110+See the \fIcurl_global_trace(3)\fP man page for more details.
5111+
5112+This option is global and does not need to be specified for each use of --next.
5113+
5114+--trace-config can be used several times in a command line
5115+
5116+Example:
5117+.nf
5118+ curl --trace-config ids,http/2 https://example.com
5119+.fi
5120+
5121+See also \fI-v, \-\-verbose\fP and \fI\-\-trace\fP. This option is mutually exclusive to \fI\-\-trace\fP and \fI-v, \-\-verbose\fP. Added in 8.3.0.
5122+.IP "\-\-trace\-ids"
5123+Prepends the transfer and connection identifiers to each trace or verbose line that curl displays.
5124+
5125+This option is global and does not need to be specified for each use of --next.
5126+
5127+Providing --trace-ids multiple times has no extra effect.
5128+Disable it again with \-\-no-trace-ids.
5129+
5130+Example:
5131+.nf
5132+ curl --trace-ids --trace-ascii output https://example.com
5133+.fi
5134+
5135+See also \fI\-\-trace\fP and \fI-v, \-\-verbose\fP. Added in 8.2.0.
5136+.IP "\-\-trace\-time"
5137+Prepends a time stamp to each trace or verbose line that curl displays.
5138+
5139+This option is global and does not need to be specified for each use of --next.
5140+
5141+Providing --trace-time multiple times has no extra effect.
5142+Disable it again with \-\-no-trace-time.
5143+
5144+Example:
5145+.nf
5146+ curl --trace-time --trace-ascii output https://example.com
5147+.fi
5148+
5149+See also \fI\-\-trace\fP and \fI-v, \-\-verbose\fP.
5150+.IP "\-\-trace <file>"
5151+Enables a full trace dump of all incoming and outgoing data, including
5152+descriptive information, to the given output file. Use "\-" as filename to have
5153+the output sent to stdout. Use "%" as filename to have the output sent to
5154+stderr.
5155+
5156+Note that verbose output of curl activities and network traffic might contain
5157+sensitive data, including user names, credentials or secret data content. Be
5158+aware and be careful when sharing trace logs with others.
5159+
5160+This option is global and does not need to be specified for each use of --next.
5161+
5162+If --trace is provided several times, the last set value is used.
5163+
5164+Example:
5165+.nf
5166+ curl --trace log.txt https://example.com
5167+.fi
5168+
5169+See also \fI\-\-trace\-ascii\fP, \fI\-\-trace\-config\fP, \fI\-\-trace\-ids\fP and \fI\-\-trace\-time\fP. This option is mutually exclusive to \fI-v, \-\-verbose\fP and \fI\-\-trace\-ascii\fP.
5170+.IP "\-\-unix\-socket <path>"
5171+(HTTP) Connect through this Unix domain socket, instead of using the network.
5172+
5173+If --unix-socket is provided several times, the last set value is used.
5174+
5175+Example:
5176+.nf
5177+ curl --unix-socket socket-path https://example.com
5178+.fi
5179+
5180+See also \fI\-\-abstract\-unix\-socket\fP.
5181+.IP "\-T, \-\-upload\-file <file>"
5182+This transfers the specified local file to the remote URL.
5183+
5184+If there is no file part in the specified URL, curl appends the local file
5185+name to the end of the URL before the operation starts. You must use a
5186+trailing slash (/) on the last directory to prove to curl that there is no
5187+file name or curl thinks that your last directory name is the remote file name
5188+to use.
5189+
5190+When putting the local file name at the end of the URL, curl ignores what is
5191+on the left side of any slash (/) or backslash (\\) used in the file name and
5192+only appends what is on the right side of the rightmost such character.
5193+
5194+Use the file name "\-" (a single dash) to use stdin instead of a given file.
5195+Alternately, the file name "." (a single period) may be specified instead of
5196+\&"\-" to use stdin in non\-blocking mode to allow reading server output while
5197+stdin is being uploaded.
5198+
5199+If this option is used with a HTTP(S) URL, the PUT method is used.
5200+
5201+You can specify one \fI\-T, \-\-upload\-file\fP for each URL on the command line. Each
5202+\fI\-T, \-\-upload\-file\fP + URL pair specifies what to upload and to where. curl also
5203+supports "globbing" of the \fI\-T, \-\-upload\-file\fP argument, meaning that you can upload
5204+multiple files to a single URL by using the same URL globbing style supported
5205+in the URL.
5206+
5207+When uploading to an SMTP server: the uploaded data is assumed to be RFC 5322
5208+formatted. It has to feature the necessary set of headers and mail body
5209+formatted correctly by the user as curl does not transcode nor encode it
5210+further in any way.
5211+
5212+--upload-file can be used several times in a command line
5213+
5214+Examples:
5215+.nf
5216+ curl -T file https://example.com
5217+ curl -T "img[1-1000].png" ftp://ftp.example.com/
5218+ curl --upload-file "{file1,file2}" https://example.com
5219+.fi
5220+
5221+See also \fI-G, \-\-get\fP, \fI-I, \-\-head\fP, \fI-X, \-\-request\fP and \fI-d, \-\-data\fP.
5222+.IP "\-\-url\-query <data>"
5223+(all) This option adds a piece of data, usually a name + value pair, to the end of
5224+the URL query part. The syntax is identical to that used for \fI\-\-data\-urlencode\fP
5225+with one extension:
5226+
5227+If the argument starts with a \(aq+\(aq (plus), the rest of the string is provided
5228+as\-is unencoded.
5229+
5230+The query part of a URL is the one following the question mark on the right
5231+end.
5232+
5233+--url-query can be used several times in a command line
5234+
5235+Examples:
5236+.nf
5237+ curl --url-query name=val https://example.com
5238+ curl --url-query =encodethis http://example.net/foo
5239+ curl --url-query name@file https://example.com
5240+ curl --url-query @fileonly https://example.com
5241+ curl --url-query "+name=%20foo" https://example.com
5242+.fi
5243+
5244+See also \fI\-\-data\-urlencode\fP and \fI-G, \-\-get\fP. Added in 7.87.0.
5245+.IP "\-\-url <url>"
5246+Specify a URL to fetch. This option is mostly handy when you want to specify
5247+URL(s) in a config file.
5248+
5249+If the given URL is missing a scheme name (such as "http://" or "ftp://" etc)
5250+then curl makes a guess based on the host. If the outermost subdomain name
5251+matches DICT, FTP, IMAP, LDAP, POP3 or SMTP then that protocol is used,
5252+otherwise HTTP is used. Guessing can be avoided by providing a full URL
5253+including the scheme, or disabled by setting a default protocol (added in
5254+7.45.0), see \fI\-\-proto\-default\fP for details.
5255+
5256+To control where this URL is written, use the \fI\-o, \-\-output\fP or the \fI\-O, \-\-remote\-name\fP
5257+options.
5258+
5259+\fBWARNING\fP: On Windows, particular file:// accesses can be converted to
5260+network accesses by the operating system. Beware!
5261+
5262+--url can be used several times in a command line
5263+
5264+Example:
5265+.nf
5266+ curl --url https://example.com
5267+.fi
5268+
5269+See also \fI-:, \-\-next\fP and \fI-K, \-\-config\fP.
5270+.IP "\-B, \-\-use\-ascii"
5271+(FTP LDAP) Enable ASCII transfer. For FTP, this can also be enforced by using a URL that
5272+ends with ";type=A". This option causes data sent to stdout to be in text mode
5273+for win32 systems.
5274+
5275+Providing --use-ascii multiple times has no extra effect.
5276+Disable it again with \-\-no-use-ascii.
5277+
5278+Example:
5279+.nf
5280+ curl -B ftp://example.com/README
5281+.fi
5282+
5283+See also \fI\-\-crlf\fP and \fI\-\-data\-ascii\fP.
5284+.IP "\-A, \-\-user\-agent <name>"
5285+(HTTP) Specify the User\-Agent string to send to the HTTP server. To encode blanks in
5286+the string, surround the string with single quote marks. This header can also
5287+be set with the \fI\-H, \-\-header\fP or the \fI\-\-proxy\-header\fP options.
5288+
5289+If you give an empty argument to \fI\-A, \-\-user\-agent\fP (""), it removes the header
5290+completely from the request. If you prefer a blank header, you can set it to a
5291+single space (" ").
5292+
5293+If --user-agent is provided several times, the last set value is used.
5294+
5295+Example:
5296+.nf
5297+ curl -A "Agent 007" https://example.com
5298+.fi
5299+
5300+See also \fI-H, \-\-header\fP and \fI\-\-proxy\-header\fP.
5301+.IP "\-u, \-\-user <user:password>"
5302+Specify the user name and password to use for server authentication. Overrides
5303+\fI\-n, \-\-netrc\fP and \fI\-\-netrc\-optional\fP.
5304+
5305+If you simply specify the user name, curl prompts for a password.
5306+
5307+The user name and passwords are split up on the first colon, which makes it
5308+impossible to use a colon in the user name with this option. The password can,
5309+still.
5310+
5311+On systems where it works, curl hides the given option argument from process
5312+listings. This is not enough to protect credentials from possibly getting seen
5313+by other users on the same system as they still are visible for a moment
5314+before cleared. Such sensitive data should be retrieved from a file instead or
5315+similar and never used in clear text in a command line.
5316+
5317+When using Kerberos V5 with a Windows based server you should include the
5318+Windows domain name in the user name, in order for the server to successfully
5319+obtain a Kerberos Ticket. If you do not, then the initial authentication
5320+handshake may fail.
5321+
5322+When using NTLM, the user name can be specified simply as the user name,
5323+without the domain, if there is a single domain and forest in your setup
5324+for example.
5325+
5326+To specify the domain name use either Down\-Level Logon Name or UPN (User
5327+Principal Name) formats. For example, EXAMPLE\\user and user@example.com
5328+respectively.
5329+
5330+If you use a Windows SSPI\-enabled curl binary and perform Kerberos V5,
5331+Negotiate, NTLM or Digest authentication then you can tell curl to select
5332+the user name and password from your environment by specifying a single colon
5333+with this option: "\-u :".
5334+
5335+If --user is provided several times, the last set value is used.
5336+
5337+Example:
5338+.nf
5339+ curl -u user:secret https://example.com
5340+.fi
5341+
5342+See also \fI-n, \-\-netrc\fP and \fI-K, \-\-config\fP.
5343+.IP "\-\-variable <[%]name=text/@file>"
5344+Set a variable with "name=content" or "name@file" (where "file" can be stdin
5345+if set to a single dash (\-)). The name is a case sensitive identifier that
5346+must consist of no other letters than a\-z, A\-Z, 0\-9 or underscore. The
5347+specified content is then associated with this identifier.
5348+
5349+Setting the same variable name again overwrites the old contents with the new.
5350+
5351+The contents of a variable can be referenced in a later command line option
5352+when that option name is prefixed with "\--expand\-", and the name is used as
5353+\&"{{name}}" (without the quotes).
5354+
5355+\fI\-\-variable\fP can import environment variables into the name space. Opt to either
5356+require the environment variable to be set or provide a default value for the
5357+variable in case it is not already set.
5358+
5359+\fI\-\-variable\fP %name imports the variable called \(aqname\(aq but exits with an error if
5360+that environment variable is not already set. To provide a default value if
5361+the environment variable is not set, use \fI\-\-variable\fP %name=content or
5362+\fI\-\-variable\fP %name@content. Note that on some systems \- but not all \-
5363+environment variables are case insensitive.
5364+
5365+When expanding variables, curl supports a set of functions that can make the
5366+variable contents more convenient to use. You apply a function to a variable
5367+expansion by adding a colon and then list the desired functions in a
5368+comma\-separated list that is evaluated in a left\-to\-right order. Variable
5369+content holding null bytes that are not encoded when expanded, causes an
5370+error.
5371+
5372+Available functions:
5373+.RS
5374+.IP trim
5375+removes all leading and trailing white space.
5376+.IP json
5377+outputs the content using JSON string quoting rules.
5378+.IP url
5379+shows the content URL (percent) encoded.
5380+.IP b64
5381+expands the variable base64 encoded
5382+.RE
5383+.IP
5384+
5385+--variable can be used several times in a command line
5386+
5387+Example:
5388+.nf
5389+ curl --variable name=smith https://example.com
5390+.fi
5391+
5392+See also \fI-K, \-\-config\fP. Added in 8.3.0.
5393+.IP "\-v, \-\-verbose"
5394+Makes curl verbose during the operation. Useful for debugging and seeing
5395+what\(aqs going on "under the hood". A line starting with \(aq>\(aq means "header data"
5396+sent by curl, \(aq<\(aq means "header data" received by curl that is hidden in
5397+normal cases, and a line starting with \(aq*\(aq means additional info provided by
5398+curl.
5399+
5400+If you only want HTTP headers in the output, \fI\-i, \-\-include\fP or \fI\-D, \-\-dump\-header\fP might
5401+be more suitable options.
5402+
5403+If you think this option still does not give you enough details, consider using
5404+\fI\-\-trace\fP or \fI\-\-trace\-ascii\fP instead.
5405+
5406+Note that verbose output of curl activities and network traffic might contain
5407+sensitive data, including user names, credentials or secret data content. Be
5408+aware and be careful when sharing trace logs with others.
5409+
5410+This option is global and does not need to be specified for each use of --next.
5411+
5412+Providing --verbose multiple times has no extra effect.
5413+Disable it again with \-\-no-verbose.
5414+
5415+Example:
5416+.nf
5417+ curl --verbose https://example.com
5418+.fi
5419+
5420+See also \fI-i, \-\-include\fP, \fI-s, \-\-silent\fP, \fI\-\-trace\fP and \fI\-\-trace\-ascii\fP. This option is mutually exclusive to \fI\-\-trace\fP and \fI\-\-trace\-ascii\fP.
5421+.IP "\-V, \-\-version"
5422+Displays information about curl and the libcurl version it uses.
5423+
5424+The first line includes the full version of curl, libcurl and other 3rd party
5425+libraries linked with the executable.
5426+
5427+The second line (starts with "Release\-Date:") shows the release date.
5428+
5429+The third line (starts with "Protocols:") shows all protocols that libcurl
5430+reports to support.
5431+
5432+The fourth line (starts with "Features:") shows specific features libcurl
5433+reports to offer. Available features include:
5434+.RS
5435+.IP `alt-svc`
5436+Support for the Alt\-Svc: header is provided.
5437+.IP `AsynchDNS`
5438+This curl uses asynchronous name resolves. Asynchronous name resolves can be
5439+done using either the c\-ares or the threaded resolver backends.
5440+.IP `brotli`
5441+Support for automatic brotli compression over HTTP(S).
5442+.IP `CharConv`
5443+curl was built with support for character set conversions (like EBCDIC)
5444+.IP `Debug`
5445+This curl uses a libcurl built with Debug. This enables more error\-tracking
5446+and memory debugging etc. For curl\-developers only!
5447+.IP `gsasl`
5448+The built\-in SASL authentication includes extensions to support SCRAM because
5449+libcurl was built with libgsasl.
5450+.IP `GSS-API`
5451+GSS\-API is supported.
5452+.IP `HSTS`
5453+HSTS support is present.
5454+.IP `HTTP2`
5455+HTTP/2 support has been built\-in.
5456+.IP `HTTP3`
5457+HTTP/3 support has been built\-in.
5458+.IP `HTTPS-proxy`
5459+This curl is built to support HTTPS proxy.
5460+.IP `IDN`
5461+This curl supports IDN \- international domain names.
5462+.IP `IPv6`
5463+You can use IPv6 with this.
5464+.IP `Kerberos`
5465+Kerberos V5 authentication is supported.
5466+.IP `Largefile`
5467+This curl supports transfers of large files, files larger than 2GB.
5468+.IP `libz`
5469+Automatic decompression (via gzip, deflate) of compressed files over HTTP is
5470+supported.
5471+.IP `MultiSSL`
5472+This curl supports multiple TLS backends.
5473+.IP `NTLM`
5474+NTLM authentication is supported.
5475+.IP `NTLM_WB`
5476+NTLM delegation to winbind helper is supported.
5477+.IP `PSL`
5478+PSL is short for Public Suffix List and means that this curl has been built
5479+with knowledge about "public suffixes".
5480+.IP `SPNEGO`
5481+SPNEGO authentication is supported.
5482+.IP `SSL`
5483+SSL versions of various protocols are supported, such as HTTPS, FTPS, POP3S
5484+and so on.
5485+.IP `SSPI`
5486+SSPI is supported.
5487+.IP `TLS-SRP`
5488+SRP (Secure Remote Password) authentication is supported for TLS.
5489+.IP `TrackMemory`
5490+Debug memory tracking is supported.
5491+.IP `Unicode`
5492+Unicode support on Windows.
5493+.IP `UnixSockets`
5494+Unix sockets support is provided.
5495+.IP `zstd`
5496+Automatic decompression (via zstd) of compressed files over HTTP is supported.
5497+.RE
5498+.IP
5499+
5500+Example:
5501+.nf
5502+ curl --version
5503+.fi
5504+
5505+See also \fI-h, \-\-help\fP and \fI-M, \-\-manual\fP.
5506+.IP "\-w, \-\-write\-out <format>"
5507+Make curl display information on stdout after a completed transfer. The format
5508+is a string that may contain plain text mixed with any number of
5509+variables. The format can be specified as a literal "string", or you can have
5510+curl read the format from a file with "@filename" and to tell curl to read the
5511+format from stdin you write "@\-".
5512+
5513+The variables present in the output format are substituted by the value or
5514+text that curl thinks fit, as described below. All variables are specified as
5515+%{variable_name} and to output a normal % you just write them as %%. You can
5516+output a newline by using \\n, a carriage return with \\r and a tab space with
5517+\\t.
5518+
5519+The output is by default written to standard output, but can be changed with
5520+%{stderr} and %output{}.
5521+
5522+Output HTTP headers from the most recent request by using \fI%header{name}\fP
5523+where \fIname\fP is the case insensitive name of the header (without the trailing
5524+colon). The header contents are exactly as sent over the network, with leading
5525+and trailing whitespace trimmed (added in 7.84.0).
5526+
5527+Select a specific target destination file to write the output to, by using
5528+\fI%output{name}\fP (added in curl 8.3.0) where \fIname\fP is the full file name. The
5529+output following that instruction is then written to that file. More than one
5530+\fI%output{}\fP instruction can be specified in the same write\-out argument. If
5531+the file name cannot be created, curl leaves the output destination to the one
5532+used prior to the \fI%output{}\fP instruction. Use \fI%output{>>name}\fP to append
5533+data to an existing file.
5534+
5535+\fBNOTE:\fP
5536+In Windows the %\-symbol is a special symbol used to expand environment
5537+variables. In batch files all occurrences of % must be doubled when using this
5538+option to properly escape. If this option is used at the command prompt then
5539+the % cannot be escaped and unintended expansion is possible.
5540+
5541+The variables available are:
5542+.RS
5543+.IP `certs`
5544+Output the certificate chain with details. Supported only by the OpenSSL,
5545+GnuTLS, Schannel and Secure Transport backends. (Added in 7.88.0)
5546+.IP `content_type`
5547+The Content\-Type of the requested document, if there was any.
5548+.IP `errormsg`
5549+The error message. (Added in 7.75.0)
5550+.IP `exitcode`
5551+The numerical exit code of the transfer. (Added in 7.75.0)
5552+.IP `filename_effective`
5553+The ultimate filename that curl writes out to. This is only meaningful if curl
5554+is told to write to a file with the \fI\-O, \-\-remote\-name\fP or \fI\-o, \-\-output\fP
5555+option. It\(aqs most useful in combination with the \fI\-J, \-\-remote\-header\-name\fP
5556+option.
5557+.IP `ftp_entry_path`
5558+The initial path curl ended up in when logging on to the remote FTP
5559+server.
5560+.IP `header_json`
5561+A JSON object with all HTTP response headers from the recent transfer. Values
5562+are provided as arrays, since in the case of multiple headers there can be
5563+multiple values. (Added in 7.83.0)
5564+
5565+The header names provided in lowercase, listed in order of appearance over the
5566+wire. Except for duplicated headers. They are grouped on the first occurrence
5567+of that header, each value is presented in the JSON array.
5568+.IP `http_code`
5569+The numerical response code that was found in the last retrieved HTTP(S) or
5570+FTP(s) transfer.
5571+.IP `http_connect`
5572+The numerical code that was found in the last response (from a proxy) to a
5573+curl CONNECT request.
5574+.IP `http_version`
5575+The http version that was effectively used. (Added in 7.50.0)
5576+.IP `json`
5577+A JSON object with all available keys. (Added in 7.70.0)
5578+.IP `local_ip`
5579+The IP address of the local end of the most recently done connection \- can be
5580+either IPv4 or IPv6.
5581+.IP `local_port`
5582+The local port number of the most recently done connection.
5583+.IP `method`
5584+The http method used in the most recent HTTP request. (Added in 7.72.0)
5585+.IP `num_certs`
5586+Number of server certificates received in the TLS handshake. Supported only by
5587+the OpenSSL, GnuTLS, Schannel and Secure Transport backends.
5588+(Added in 7.88.0)
5589+.IP `num_connects`
5590+Number of new connects made in the recent transfer.
5591+.IP `num_headers`
5592+The number of response headers in the most recent request (restarted at each
5593+redirect). Note that the status line IS NOT a header. (Added in 7.73.0)
5594+.IP `num_redirects`
5595+Number of redirects that were followed in the request.
5596+.IP `onerror`
5597+The rest of the output is only shown if the transfer returned a non\-zero error.
5598+(Added in 7.75.0)
5599+.IP `proxy_ssl_verify_result`
5600+The result of the HTTPS proxy\(aqs SSL peer certificate verification that was
5601+requested. 0 means the verification was successful. (Added in 7.52.0)
5602+.IP `redirect_url`
5603+When an HTTP request was made without \fI\-L, \-\-location\fP to follow redirects (or when
5604+\fI\-\-max\-redirs\fP is met), this variable shows the actual URL a redirect
5605+\fIwould\fP have gone to.
5606+.IP `referer`
5607+The Referer: header, if there was any. (Added in 7.76.0)
5608+.IP `remote_ip`
5609+The remote IP address of the most recently done connection \- can be either
5610+IPv4 or IPv6.
5611+.IP `remote_port`
5612+The remote port number of the most recently done connection.
5613+.IP `response_code`
5614+The numerical response code that was found in the last transfer (formerly
5615+known as "http_code").
5616+.IP `scheme`
5617+The URL scheme (sometimes called protocol) that was effectively used. (Added in 7.52.0)
5618+.IP `size_download`
5619+The total amount of bytes that were downloaded. This is the size of the
5620+body/data that was transferred, excluding headers.
5621+.IP `size_header`
5622+The total amount of bytes of the downloaded headers.
5623+.IP `size_request`
5624+The total amount of bytes that were sent in the HTTP request.
5625+.IP `size_upload`
5626+The total amount of bytes that were uploaded. This is the size of the
5627+body/data that was transferred, excluding headers.
5628+.IP `speed_download`
5629+The average download speed that curl measured for the complete download. Bytes
5630+per second.
5631+.IP `speed_upload`
5632+The average upload speed that curl measured for the complete upload. Bytes per
5633+second.
5634+.IP `ssl_verify_result`
5635+The result of the SSL peer certificate verification that was requested. 0
5636+means the verification was successful.
5637+.IP `stderr`
5638+From this point on, the \fI\-w, \-\-write\-out\fP output is written to standard
5639+error. (Added in 7.63.0)
5640+.IP `stdout`
5641+From this point on, the \fI\-w, \-\-write\-out\fP output is written to standard output.
5642+This is the default, but can be used to switch back after switching to stderr.
5643+(Added in 7.63.0)
5644+.IP `time_appconnect`
5645+The time, in seconds, it took from the start until the SSL/SSH/etc
5646+connect/handshake to the remote host was completed.
5647+.IP `time_connect`
5648+The time, in seconds, it took from the start until the TCP connect to the
5649+remote host (or proxy) was completed.
5650+.IP `time_namelookup`
5651+The time, in seconds, it took from the start until the name resolving was
5652+completed.
5653+.IP `time_pretransfer`
5654+The time, in seconds, it took from the start until the file transfer was just
5655+about to begin. This includes all pre\-transfer commands and negotiations that
5656+are specific to the particular protocol(s) involved.
5657+.IP `time_redirect`
5658+The time, in seconds, it took for all redirection steps including name lookup,
5659+connect, pretransfer and transfer before the final transaction was
5660+started. "time_redirect" shows the complete execution time for multiple
5661+redirections.
5662+.IP `time_starttransfer`
5663+The time, in seconds, it took from the start until the first byte is received.
5664+This includes time_pretransfer and also the time the server needed to calculate
5665+the result.
5666+.IP `time_total`
5667+The total time, in seconds, that the full operation lasted.
5668+.IP `url`
5669+The URL that was fetched. (Added in 7.75.0)
5670+.IP `url.scheme`
5671+The scheme part of the URL that was fetched. (Added in 8.1.0)
5672+.IP `url.user`
5673+The user part of the URL that was fetched. (Added in 8.1.0)
5674+.IP `url.password`
5675+The password part of the URL that was fetched. (Added in 8.1.0)
5676+.IP `url.options`
5677+The options part of the URL that was fetched. (Added in 8.1.0)
5678+.IP `url.host`
5679+The host part of the URL that was fetched. (Added in 8.1.0)
5680+.IP `url.port`
5681+The port number of the URL that was fetched. If no port number was specified
5682+and the URL scheme is known, that scheme\(aqs default port number is
5683+shown. (Added in 8.1.0)
5684+.IP `url.path`
5685+The path part of the URL that was fetched. (Added in 8.1.0)
5686+.IP `url.query`
5687+The query part of the URL that was fetched. (Added in 8.1.0)
5688+.IP `url.fragment`
5689+The fragment part of the URL that was fetched. (Added in 8.1.0)
5690+.IP `url.zoneid`
5691+The zone id part of the URL that was fetched. (Added in 8.1.0)
5692+.IP `urle.scheme`
5693+The scheme part of the effective (last) URL that was fetched. (Added in 8.1.0)
5694+.IP `urle.user`
5695+The user part of the effective (last) URL that was fetched. (Added in 8.1.0)
5696+.IP `urle.password`
5697+The password part of the effective (last) URL that was fetched. (Added in 8.1.0)
5698+.IP `urle.options`
5699+The options part of the effective (last) URL that was fetched. (Added in 8.1.0)
5700+.IP `urle.host`
5701+The host part of the effective (last) URL that was fetched. (Added in 8.1.0)
5702+.IP `urle.port`
5703+The port number of the effective (last) URL that was fetched. If no port
5704+number was specified, but the URL scheme is known, that scheme\(aqs default port
5705+number is shown. (Added in 8.1.0)
5706+.IP `urle.path`
5707+The path part of the effective (last) URL that was fetched. (Added in 8.1.0)
5708+.IP `urle.query`
5709+The query part of the effective (last) URL that was fetched. (Added in 8.1.0)
5710+.IP `urle.fragment`
5711+The fragment part of the effective (last) URL that was fetched. (Added in 8.1.0)
5712+.IP `urle.zoneid`
5713+The zone id part of the effective (last) URL that was fetched. (Added in 8.1.0)
5714+.IP `urlnum`
5715+The URL index number of this transfer, 0\-indexed. Unglobbed URLs share the
5716+same index number as the origin globbed URL. (Added in 7.75.0)
5717+.IP `url_effective`
5718+The URL that was fetched last. This is most meaningful if you have told curl
5719+to follow location: headers.
5720+.RE
5721+.IP
5722+
5723+If --write-out is provided several times, the last set value is used.
5724+
5725+Example:
5726+.nf
5727+ curl -w '%{response_code}\\n' https://example.com
5728+.fi
5729+
5730+See also \fI-v, \-\-verbose\fP and \fI-I, \-\-head\fP.
5731+.IP "\-\-xattr"
5732+When saving output to a file, this option tells curl to store certain file
5733+metadata in extended file attributes. Currently, the URL is stored in the
5734+\&"xdg.origin.url" attribute and, for HTTP, the content type is stored in the
5735+\&"mime_type" attribute. If the file system does not support extended
5736+attributes, a warning is issued.
5737+
5738+Providing --xattr multiple times has no extra effect.
5739+Disable it again with \-\-no-xattr.
5740+
5741+Example:
5742+.nf
5743+ curl --xattr -o storage https://example.com
5744+.fi
5745+
5746+See also \fI-R, \-\-remote\-time\fP, \fI-w, \-\-write\-out\fP and \fI-v, \-\-verbose\fP.
5747+.SH FILES
5748+\fI~/.curlrc\fP
5749+
5750+Default config file, see \fI\-K, \-\-config\fP for details.
5751+.SH ENVIRONMENT
5752+The environment variables can be specified in lower case or upper case. The
5753+lower case version has precedence. "http_proxy" is an exception as it is only
5754+available in lower case.
5755+
5756+Using an environment variable to set the proxy has the same effect as using
5757+the \fI\-x, \-\-proxy\fP option.
5758+.IP "`http_proxy` [protocol://]<host>[:port]"
5759+Sets the proxy server to use for HTTP.
5760+.IP "`HTTPS_PROXY` [protocol://]<host>[:port]"
5761+Sets the proxy server to use for HTTPS.
5762+.IP "`[url-protocol]_PROXY` [protocol://]<host>[:port]"
5763+Sets the proxy server to use for [url\-protocol], where the protocol is a
5764+protocol that curl supports and as specified in a URL. FTP, FTPS, POP3, IMAP,
5765+SMTP, LDAP, etc.
5766+.IP "`ALL_PROXY` [protocol://]<host>[:port]"
5767+Sets the proxy server to use if no protocol\-specific proxy is set.
5768+.IP "`NO_PROXY` <comma-separated list of hosts/domains>"
5769+list of host names that should not go through any proxy. If set to an asterisk
5770+\(aq*\(aq only, it matches all hosts. Each name in this list is matched as either
5771+a domain name which contains the hostname, or the hostname itself.
5772+
5773+This environment variable disables use of the proxy even when specified with
5774+the \fI\-x, \-\-proxy\fP option. That is
5775+.nf
5776+
5777+NO_PROXY=direct.example.com curl \-x http://proxy.example.com
5778+http://direct.example.com
5779+.fi
5780+
5781+accesses the target URL directly, and
5782+.nf
5783+
5784+NO_PROXY=direct.example.com curl \-x http://proxy.example.com
5785+http://somewhere.example.com
5786+.fi
5787+
5788+accesses the target URL through the proxy.
5789+
5790+The list of host names can also be include numerical IP addresses, and IPv6
5791+versions should then be given without enclosing brackets.
5792+
5793+IP addresses can be specified using CIDR notation: an appended slash and
5794+number specifies the number of "network bits" out of the address to use in the
5795+comparison (added in 7.86.0). For example "192.168.0.0/16" would match all
5796+addresses starting with "192.168".
5797+.IP "`APPDATA` <dir>"
5798+On Windows, this variable is used when trying to find the home directory. If
5799+the primary home variable are all unset.
5800+.IP "`COLUMNS` <terminal width>"
5801+If set, the specified number of characters is used as the terminal width when
5802+the alternative progress\-bar is shown. If not set, curl tries to figure it out
5803+using other ways.
5804+.IP "`CURL_CA_BUNDLE` <file>"
5805+If set, it is used as the \fI\-\-cacert\fP value. This environment variable is ignored
5806+if Schannel is used as the TLS backend.
5807+.IP "`CURL_HOME` <dir>"
5808+If set, is the first variable curl checks when trying to find its home
5809+directory. If not set, it continues to check \fIXDG_CONFIG_HOME\fP
5810+.IP "`CURL_SSL_BACKEND` <TLS backend>"
5811+If curl was built with support for "MultiSSL", meaning that it has built\-in
5812+support for more than one TLS backend, this environment variable can be set to
5813+the case insensitive name of the particular backend to use when curl is
5814+invoked. Setting a name that is not a built\-in alternative makes curl stay
5815+with the default.
5816+
5817+SSL backend names (case\-insensitive): \fBbearssl\fP, \fBgnutls\fP, \fBmbedtls\fP,
5818+\fBopenssl\fP, \fBrustls\fP, \fBschannel\fP, \fBsecure\-transport\fP, \fBwolfssl\fP
5819+.IP "`HOME` <dir>"
5820+If set, this is used to find the home directory when that is needed. Like when
5821+looking for the default .curlrc. \fICURL_HOME\fP and \fIXDG_CONFIG_HOME\fP
5822+have preference.
5823+.IP "`QLOGDIR` <directory name>"
5824+If curl was built with HTTP/3 support, setting this environment variable to a
5825+local directory makes curl produce \fBqlogs\fP in that directory, using file
5826+names named after the destination connection id (in hex). Do note that these
5827+files can become rather large. Works with the ngtcp2 and quiche QUIC backends.
5828+.IP `SHELL`
5829+Used on VMS when trying to detect if using a \fBDCL\fP or a \fBunix\fP shell.
5830+.IP "`SSL_CERT_DIR` <dir>"
5831+If set, it is used as the \fI\-\-capath\fP value. This environment variable is ignored
5832+if Schannel is used as the TLS backend.
5833+.IP "`SSL_CERT_FILE` <path>"
5834+If set, it is used as the \fI\-\-cacert\fP value. This environment variable is ignored
5835+if Schannel is used as the TLS backend.
5836+.IP "`SSLKEYLOGFILE` <file name>"
5837+If you set this environment variable to a file name, curl stores TLS secrets
5838+from its connections in that file when invoked to enable you to analyze the
5839+TLS traffic in real time using network analyzing tools such as Wireshark. This
5840+works with the following TLS backends: OpenSSL, libressl, BoringSSL, GnuTLS
5841+and wolfSSL.
5842+.IP "`USERPROFILE` <dir>"
5843+On Windows, this variable is used when trying to find the home directory. If
5844+the other, primary, variable are all unset. If set, curl uses the path
5845+\fB"$USERPROFILE\\Application Data"\fP.
5846+.IP "`XDG_CONFIG_HOME` <dir>"
5847+If \fICURL_HOME\fP is not set, this variable is checked when looking for a
5848+default .curlrc file.
5849+.SH PROXY PROTOCOL PREFIXES
5850+The proxy string may be specified with a protocol:// prefix to specify
5851+alternative proxy protocols.
5852+
5853+If no protocol is specified in the proxy string or if the string does not
5854+match a supported one, the proxy is treated as an HTTP proxy.
5855+
5856+The supported proxy protocol prefixes are as follows:
5857+.IP http://
5858+Makes it use it as an HTTP proxy. The default if no scheme prefix is used.
5859+.IP https://
5860+Makes it treated as an \fBHTTPS\fP proxy.
5861+.IP socks4://
5862+Makes it the equivalent of \fI\-\-socks4\fP
5863+.IP socks4a://
5864+Makes it the equivalent of \fI\-\-socks4a\fP
5865+.IP socks5://
5866+Makes it the equivalent of \fI\-\-socks5\fP
5867+.IP socks5h://
5868+Makes it the equivalent of \fI\-\-socks5\-hostname\fP
5869+.SH EXIT CODES
5870+There are a bunch of different error codes and their corresponding error
5871+messages that may appear under error conditions. At the time of this writing,
5872+the exit codes are:
5873+.IP 0
5874+Success. The operation completed successfully according to the instructions.
5875+.IP 1
5876+Unsupported protocol. This build of curl has no support for this protocol.
5877+.IP 2
5878+Failed to initialize.
5879+.IP 3
5880+URL malformed. The syntax was not correct.
5881+.IP 4
5882+A feature or option that was needed to perform the desired request was not
5883+enabled or was explicitly disabled at build\-time. To make curl able to do
5884+this, you probably need another build of libcurl.
5885+.IP 5
5886+Could not resolve proxy. The given proxy host could not be resolved.
5887+.IP 6
5888+Could not resolve host. The given remote host could not be resolved.
5889+.IP 7
5890+Failed to connect to host.
5891+.IP 8
5892+Weird server reply. The server sent data curl could not parse.
5893+.IP 9
5894+FTP access denied. The server denied login or denied access to the particular
5895+resource or directory you wanted to reach. Most often you tried to change to a
5896+directory that does not exist on the server.
5897+.IP 10
5898+FTP accept failed. While waiting for the server to connect back when an active
5899+FTP session is used, an error code was sent over the control connection or
5900+similar.
5901+.IP 11
5902+FTP weird PASS reply. Curl could not parse the reply sent to the PASS request.
5903+.IP 12
5904+During an active FTP session while waiting for the server to connect back to
5905+curl, the timeout expired.
5906+.IP 13
5907+FTP weird PASV reply, Curl could not parse the reply sent to the PASV request.
5908+.IP 14
5909+FTP weird 227 format. Curl could not parse the 227\-line the server sent.
5910+.IP 15
5911+FTP cannot use host. Could not resolve the host IP we got in the 227\-line.
5912+.IP 16
5913+HTTP/2 error. A problem was detected in the HTTP2 framing layer. This is
5914+somewhat generic and can be one out of several problems, see the error message
5915+for details.
5916+.IP 17
5917+FTP could not set binary. Could not change transfer method to binary.
5918+.IP 18
5919+Partial file. Only a part of the file was transferred.
5920+.IP 19
5921+FTP could not download/access the given file, the RETR (or similar) command
5922+failed.
5923+.IP 21
5924+FTP quote error. A quote command returned error from the server.
5925+.IP 22
5926+HTTP page not retrieved. The requested URL was not found or returned another
5927+error with the HTTP error code being 400 or above. This return code only
5928+appears if \fI\-f, \-\-fail\fP is used.
5929+.IP 23
5930+Write error. Curl could not write data to a local filesystem or similar.
5931+.IP 25
5932+Failed starting the upload. For FTP, the server typically denied the STOR
5933+command.
5934+.IP 26
5935+Read error. Various reading problems.
5936+.IP 27
5937+Out of memory. A memory allocation request failed.
5938+.IP 28
5939+Operation timeout. The specified time\-out period was reached according to the
5940+conditions.
5941+.IP 30
5942+FTP PORT failed. The PORT command failed. Not all FTP servers support the PORT
5943+command, try doing a transfer using PASV instead.
5944+.IP 31
5945+FTP could not use REST. The REST command failed. This command is used for
5946+resumed FTP transfers.
5947+.IP 33
5948+HTTP range error. The range "command" did not work.
5949+.IP 34
5950+HTTP post error. Internal post\-request generation error.
5951+.IP 35
5952+SSL connect error. The SSL handshaking failed.
5953+.IP 36
5954+Bad download resume. Could not continue an earlier aborted download.
5955+.IP 37
5956+FILE could not read file. Failed to open the file. Permissions?
5957+.IP 38
5958+LDAP cannot bind. LDAP bind operation failed.
5959+.IP 39
5960+LDAP search failed.
5961+.IP 41
5962+Function not found. A required LDAP function was not found.
5963+.IP 42
5964+Aborted by callback. An application told curl to abort the operation.
5965+.IP 43
5966+Internal error. A function was called with a bad parameter.
5967+.IP 45
5968+Interface error. A specified outgoing interface could not be used.
5969+.IP 47
5970+Too many redirects. When following redirects, curl hit the maximum amount.
5971+.IP 48
5972+Unknown option specified to libcurl. This indicates that you passed a weird
5973+option to curl that was passed on to libcurl and rejected. Read up in the
5974+manual!
5975+.IP 49
5976+Malformed telnet option.
5977+.IP 52
5978+The server did not reply anything, which here is considered an error.
5979+.IP 53
5980+SSL crypto engine not found.
5981+.IP 54
5982+Cannot set SSL crypto engine as default.
5983+.IP 55
5984+Failed sending network data.
5985+.IP 56
5986+Failure in receiving network data.
5987+.IP 58
5988+Problem with the local certificate.
5989+.IP 59
5990+Could not use specified SSL cipher.
5991+.IP 60
5992+Peer certificate cannot be authenticated with known CA certificates.
5993+.IP 61
5994+Unrecognized transfer encoding.
5995+.IP 63
5996+Maximum file size exceeded.
5997+.IP 64
5998+Requested FTP SSL level failed.
5999+.IP 65
6000+Sending the data requires a rewind that failed.
6001+.IP 66
6002+Failed to initialize SSL Engine.
6003+.IP 67
6004+The user name, password, or similar was not accepted and curl failed to log in.
6005+.IP 68
6006+File not found on TFTP server.
6007+.IP 69
6008+Permission problem on TFTP server.
6009+.IP 70
6010+Out of disk space on TFTP server.
6011+.IP 71
6012+Illegal TFTP operation.
6013+.IP 72
6014+Unknown TFTP transfer ID.
6015+.IP 73
6016+File already exists (TFTP).
6017+.IP 74
6018+No such user (TFTP).
6019+.IP 77
6020+Problem reading the SSL CA cert (path? access rights?).
6021+.IP 78
6022+The resource referenced in the URL does not exist.
6023+.IP 79
6024+An unspecified error occurred during the SSH session.
6025+.IP 80
6026+Failed to shut down the SSL connection.
6027+.IP 82
6028+Could not load CRL file, missing or wrong format.
6029+.IP 83
6030+Issuer check failed.
6031+.IP 84
6032+The FTP PRET command failed.
6033+.IP 85
6034+Mismatch of RTSP CSeq numbers.
6035+.IP 86
6036+Mismatch of RTSP Session Identifiers.
6037+.IP 87
6038+Unable to parse FTP file list.
6039+.IP 88
6040+FTP chunk callback reported error.
6041+.IP 89
6042+No connection available, the session is queued.
6043+.IP 90
6044+SSL public key does not matched pinned public key.
6045+.IP 91
6046+Invalid SSL certificate status.
6047+.IP 92
6048+Stream error in HTTP/2 framing layer.
6049+.IP 93
6050+An API function was called from inside a callback.
6051+.IP 94
6052+An authentication function returned an error.
6053+.IP 95
6054+A problem was detected in the HTTP/3 layer. This is somewhat generic and can
6055+be one out of several problems, see the error message for details.
6056+.IP 96
6057+QUIC connection error. This error may be caused by an SSL library error. QUIC
6058+is the protocol used for HTTP/3 transfers.
6059+.IP 97
6060+Proxy handshake error.
6061+.IP 98
6062+A client\-side certificate is required to complete the TLS handshake.
6063+.IP 99
6064+Poll or select returned fatal error.
6065+.IP XX
6066+More error codes might appear here in future releases. The existing ones are
6067+meant to never change.
6068+.SH BUGS
6069+If you experience any problems with curl, submit an issue in the project\(aqs bug
6070+tracker on GitHub: https://github.com/curl/curl/issues
6071+.SH AUTHORS
6072+Daniel Stenberg is the main author, but the whole list of contributors is
6073+found in the separate THANKS file.
6074+.SH WWW
6075+https://curl.se
6076+.SH SEE ALSO
6077+\fBftp (1)\fP, \fBwget (1)\fP
+13,
-11
1@@ -48,7 +48,7 @@
2 #define CURL_SA_FAMILY_T sa_family_t
3 /* #undef CURL_WITH_MULTI_SSL */
4 /* #undef DEBUGBUILD */
5-#define ENABLE_IPV6 1
6+/* #undef ENABLE_IPV6 */
7 #define GETHOSTNAME_TYPE_ARG2 size_t
8 #define HAVE_ALARM 1
9 /* #undef HAVE_ARC4RANDOM */
10@@ -105,8 +105,6 @@
11 /* #undef HAVE_GSSAPI_GSSAPI_H */
12 /* #undef HAVE_GSSAPI_GSSAPI_KRB5_H */
13 /* #undef HAVE_GSSGNU */
14-/* #undef HAVE_GSSHEIMDAL */
15-/* #undef HAVE_GSSMIT */
16 /* #undef HAVE_HYPER_H */
17 /* #undef HAVE_IDN2_H */
18 #define HAVE_IFADDRS_H 1
19@@ -161,6 +159,7 @@
20 /* #undef HAVE_OPENSSL_CRYPTO_H */
21 /* #undef HAVE_OPENSSL_ERR_H */
22 /* #undef HAVE_OPENSSL_PEM_H */
23+/* #undef HAVE_OPENSSL_QUIC */
24 /* #undef HAVE_OPENSSL_RSA_H */
25 /* #undef HAVE_OPENSSL_SRP */
26 /* #undef HAVE_OPENSSL_SSL_H */
27@@ -190,13 +189,14 @@
28 #define HAVE_SIGNAL 1
29 #define HAVE_SIGSETJMP 1
30 #define HAVE_SNPRINTF 1
31-#define HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID 1
32+/* #undef HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID */
33 #define HAVE_SOCKET 1
34 #define HAVE_SOCKETPAIR 1
35 /* #undef HAVE_SOCKET_H */
36 /* #undef HAVE_SSL_GET_ECH_STATUS */
37 /* #undef HAVE_SSL_H */
38 /* #undef HAVE_SSL_SET0_WBIO */
39+/* #undef HAVE_SSL_SET_QUIC_USE_LEGACY_CODEPOINT */
40 #define HAVE_STDATOMIC_H 1
41 #define HAVE_STDBOOL_H 1
42 #define HAVE_STDINT_H 1
43@@ -237,15 +237,12 @@
44 #define HAVE_UTIME 1
45 #define HAVE_UTIMES 1
46 #define HAVE_UTIME_H 1
47-/* #undef HAVE_WINDOWS_H */
48-/* #undef HAVE_WINSOCK2_H */
49 /* #undef HAVE_WOLFSSH_SSH_H */
50 /* #undef HAVE_WOLFSSL_DES_ECB_ENCRYPT */
51 /* #undef HAVE_WOLFSSL_FULL_BIO */
52 /* #undef HAVE_WOLFSSL_GET_PEER_CERTIFICATE */
53 /* #undef HAVE_WOLFSSL_USEALPN */
54 #define HAVE_WRITABLE_ARGV 1
55-/* #undef HAVE_WS2TCPIP_H */
56 /* #undef HAVE_X509_H */
57 /* #undef HAVE_ZSTD */
58 /* #undef HAVE_ZSTD_H */
59@@ -256,7 +253,7 @@
60 /* #undef NEED_THREAD_SAFE */
61 /* #undef NTLM_WB_ENABLED */
62 /* #undef NTLM_WB_FILE */
63-#define OS "oasis"
64+#define OS "x86_64-pc-linux-musl"
65 #define PACKAGE "curl"
66 #define PACKAGE_BUGREPORT "a suitable curl mailing list: https://curl.se/mail/"
67 #define PACKAGE_NAME "curl"
68@@ -268,11 +265,11 @@
69 #define SIZEOF_CURL_OFF_T 8
70 #define SIZEOF_CURL_SOCKET_T 4
71 #define SIZEOF_INT 4
72-/* probe SIZEOF_LONG */
73+#define SIZEOF_LONG 8
74 /* #undef SIZEOF_LONG_LONG */
75 #define SIZEOF_OFF_T 8
76-/* probe SIZEOF_SIZE_T */
77-/* probe SIZEOF_TIME_T */
78+#define SIZEOF_SIZE_T 8
79+#define SIZEOF_TIME_T 8
80 #define STDC_HEADERS 1
81 /* #undef USE_AMISSL */
82 /* #undef USE_ARES */
83@@ -291,11 +288,15 @@
84 /* #undef USE_NGHTTP2 */
85 /* #undef USE_NGHTTP3 */
86 /* #undef USE_NGTCP2 */
87+/* #undef USE_NGTCP2_CRYPTO_BORINGSSL */
88 /* #undef USE_NGTCP2_CRYPTO_GNUTLS */
89 /* #undef USE_NGTCP2_CRYPTO_QUICTLS */
90 /* #undef USE_NGTCP2_CRYPTO_WOLFSSL */
91+/* #undef USE_NGTCP2_H3 */
92 /* #undef USE_OPENLDAP */
93 /* #undef USE_OPENSSL */
94+/* #undef USE_OPENSSL_H3 */
95+/* #undef USE_OPENSSL_QUIC */
96 /* #undef USE_QUICHE */
97 /* #undef USE_RUSTLS */
98 /* #undef USE_SCHANNEL */
99@@ -304,6 +305,7 @@
100 /* #undef USE_THREADS_WIN32 */
101 /* #undef USE_TLS_SRP */
102 #define USE_UNIX_SOCKETS 1
103+/* enable websockets support */
104 /* #undef USE_WEBSOCKETS */
105 /* #undef USE_WIN32_CRYPTO */
106 /* #undef USE_WIN32_IDN */
+1,
-1
1@@ -128,6 +128,6 @@ exe('curl', [[
2 ]])
3
4 file('bin/curl', '755', '$outdir/curl')
5-man{'docs/curl.1'}
6+man{'$dir/curl.1'}
7
8 fetch 'curl'
+1,
-1
1@@ -1 +1 @@
2-05fc17ff25b793a437a0906e0484b82172a9f4de02be5ed447e0cab8c3475add curl-8.5.0.tar.gz
3+9c6db808160015f30f3c656c0dec125feb9dc00753596bf858a272b5dd8dc398 curl-8.6.0.tar.gz
+1,
-1
1@@ -1 +1 @@
2-url = "https://curl.se/download/curl-8.5.0.tar.gz"
3+url = "https://curl.se/download/curl-8.6.0.tar.gz"
+1,
-1
1@@ -1 +1 @@
2-8.5.0 r0
3+8.6.0 r0