commit 48dbdcd
hovercats
·
2024-03-29 17:59:34 +0000 UTC
parent 71928db
curl: 8.7.1
8 files changed,
+651,
-619
+2,
-1
1@@ -1,2 +1,3 @@
2-/curl-8.6.0.tar.gz
3+/curl-8.7.1.tar.gz
4+/curl.1.gz
5 /src
+1,
-0
1@@ -9,6 +9,7 @@ Generated with
2 --with-ca-bundle=/etc/ssl/cert.pem \
3 --with-bearssl \
4 --without-libpsl \
5+ --enable-docs \
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
+618,
-590
1@@ -22,9 +22,9 @@
2 .\" *
3 .\" **************************************************************************
4 .\"
5-.\" DO NOT EDIT. Generated by the curl project gen.pl man page generator.
6+.\" DO NOT EDIT. Generated by the curl project managen man page generator.
7 .\"
8-.TH curl 1 "February 02 2024" "curl 8.6.0" "curl Manual"
9+.TH curl 1 "March 28 2024" "curl 8.7.1" "curl Manual"
10 .SH NAME
11 curl \- transfer a URL
12 .SH SYNOPSIS
13@@ -43,8 +43,8 @@ RFC 3986.
14
15 If you provide a URL without a leading \fBprotocol://\fP scheme, curl guesses
16 what protocol you want. It then defaults to HTTP but assumes others based on
17-often\-used host name prefixes. For example, for host names starting with
18-\&"ftp." curl assumes you want FTP.
19+often\-used hostname prefixes. For example, for hostnames starting with "ftp."
20+curl assumes you want FTP.
21
22 You can specify any amount of URLs on the command line. They are fetched in a
23 sequential manner in the specified order unless you use \fI\-Z, \-\-parallel\fP. You can
24@@ -120,11 +120,11 @@ curl supports command line variables (added in 8.3.0). Set variables with
25 \fI\-\-variable\fP name=content or \fI\-\-variable\fP name@file (where "file" can be stdin if
26 set to a single dash (\-)).
27
28-Variable contents can be expanded in option parameters using "{{name}}" (without
29-the quotes) if the option name is prefixed with "\--expand\-". This gets the
30-contents of the variable "name" inserted, or a blank if the name does not
31-exist as a variable. Insert "{{" verbatim in the string by prefixing it with a
32-backslash, like "\\{{".
33+Variable contents can be expanded in option parameters using "{{name}}" if the
34+option name is prefixed with "\fI\-\-expand\-\fP". This gets the contents of the
35+variable "name" inserted, or a blank if the name does not exist as a
36+variable. Insert "{{" verbatim in the string by prefixing it with a backslash,
37+like "\\{{".
38
39 You an access and expand environment variables by first importing them. You
40 can select to either require the environment variable to be set or you can
41@@ -143,15 +143,15 @@ set:
42
43 When expanding variables, curl supports a set of functions that can make the
44 variable contents more convenient to use. It can trim leading and trailing
45-white space with \fItrim\fP, it can output the contents as a JSON quoted string
46-with \fIjson\fP, URL encode the string with \fIurl\fP or base64 encode it with
47-\fIb64\fP. You apply function to a variable expansion, add them colon separated to
48-the right side of the variable. Variable content holding null bytes that are
49-not encoded when expanded cause error.
50+white space with "trim", it can output the contents as a JSON quoted string
51+with "json", URL encode the string with "url" or base64 encode it with "b64".
52+To apply functions to a variable expansion, add them colon separated to the
53+right side of the variable. Variable content holding null bytes that are not
54+encoded when expanded cause error.
55
56 Example: get the contents of a file called $HOME/.secret into a variable
57-called "fix". Make sure that the content is trimmed and percent\-encoded sent
58-as POST data:
59+called "fix". Make sure that the content is trimmed and percent\-encoded when
60+sent as POST data:
61 .nf
62
63 -\-variable %HOME
64@@ -160,7 +160,7 @@ as POST data:
65 https://example.com/
66 .fi
67
68-Command line variables and expansions were added in in 8.3.0.
69+Command line variables and expansions were added in 8.3.0.
70 .SH OUTPUT
71 If not told otherwise, curl writes the received data to stdout. It can be
72 instructed to instead save that data into a local file, using the \fI\-o, \-\-output\fP or
73@@ -189,14 +189,14 @@ curl supports HTTP with numerous options and variations. It can speak HTTP
74 version 0.9, 1.0, 1.1, 2 and 3 depending on build options and the correct
75 command line options.
76 .IP IMAP(S)
77-Using the mail reading protocol, curl can "download" emails for you. With or
78+Using the mail reading protocol, curl can download emails for you. With or
79 without using TLS.
80 .IP LDAP(S)
81 curl can do directory lookups for you, with or without TLS.
82 .IP MQTT
83-curl supports MQTT version 3. Downloading over MQTT equals "subscribe" to a
84-topic while uploading/posting equals "publish" on a topic. MQTT over TLS is
85-not supported (yet).
86+curl supports MQTT version 3. Downloading over MQTT equals subscribe to a
87+topic while uploading/posting equals publish on a topic. MQTT over TLS is not
88+supported (yet).
89 .IP POP3(S)
90 Downloading from a pop3 server means getting a mail. With or without using
91 TLS.
92@@ -215,11 +215,11 @@ curl supports SMB version 1 for upload and download.
93 Uploading contents to an SMTP server means sending an email. With or without
94 TLS.
95 .IP TELNET
96-Telling curl to fetch a telnet URL starts an interactive session where it
97-sends what it reads on stdin and outputs what the server sends it.
98+Fetching a telnet URL starts an interactive session where it sends what it
99+reads on stdin and outputs what the server sends it.
100 .IP TFTP
101 curl can do TFTP downloads and uploads.
102-.SH "PROGRESS METER"
103+.SH PROGRESS METER
104 curl normally displays a progress meter during operations, indicating the
105 amount of transferred data, transfer speeds and estimated time left, etc. The
106 progress meter displays the transfer rate in bytes per second. The suffixes
107@@ -232,20 +232,20 @@ the progress meter as otherwise it would mess up the output mixing progress
108 meter and response data.
109
110 If you want a progress meter for HTTP POST or PUT requests, you need to
111-redirect the response output to a file, using shell redirect (>), \fI\-o, \-\-output\fP or
112-similar.
113+redirect the response output to a file, using shell redirect (>), \fI\-o, \-\-output\fP
114+or similar.
115
116 This does not apply to FTP upload as that operation does not spit out any
117 response data to the terminal.
118
119-If you prefer a progress "bar" instead of the regular meter, \fI\-#, \-\-progress\-bar\fP is
120+If you prefer a progress bar instead of the regular meter, \fI\-#, \-\-progress\-bar\fP is
121 your friend. You can also disable the progress meter completely with the
122 \fI\-s, \-\-silent\fP option.
123 .SH VERSION
124-This man page describes curl %VERSION. If you use a later version, chances are
125-this man page does not fully document it. If you use an earlier version, this
126-document tries to include version information about which specific version
127-that introduced changes.
128+This man page describes curl 8.7.1. If you use a later version, chances
129+are this man page does not fully document it. If you use an earlier version,
130+this document tries to include version information about which specific
131+version that introduced changes.
132
133 You can always learn which the latest curl version is by running
134 .nf
135@@ -262,7 +262,7 @@ is presumed to be and treated as a URL.
136
137 The short "single\-dash" form of the options, \-d for example, may be used with
138 or without a space between it and its value, although a space is a recommended
139-separator. The long "double\-dash" form, \fI\-d, \-\-data\fP for example, requires a space
140+separator. The long double\-dash form, \fI\-d, \-\-data\fP for example, requires a space
141 between it and its value.
142
143 Short version options that do not need any additional values can be used
144@@ -272,16 +272,16 @@ options \fI\-O\fP, \fI\-L\fP and \fI\-v\fP at once as \fI\-OLv\fP.
145 In general, all boolean options are enabled with \--\fBoption\fP and yet again
146 disabled with \--\fBno\-\fPoption. That is, you use the same option name but
147 prefix it with "no\-". However, in this list we mostly only list and show the
148-\fI\--option\fP version of them.
149+-\-\fBoption\fP version of them.
150
151 When \fI\-:, \-\-next\fP is used, it resets the parser state and you start again with a
152-clean option state, except for the options that are "global". Global options
153+clean option state, except for the options that are global. Global options
154 retain their values and meaning even after \fI\-:, \-\-next\fP.
155
156 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.
157 .IP "\-\-abstract\-unix\-socket <path>"
158 (HTTP) Connect through an abstract Unix domain socket, instead of using the network.
159-Note: netstat shows the path of an abstract socket prefixed with \(aq@\(aq, however
160+Note: netstat shows the path of an abstract socket prefixed with "@", however
161 the <path> argument should not have this leading character.
162
163 If --abstract-unix-socket is provided several times, the last set value is used.
164@@ -292,13 +292,13 @@ Example:
165 .fi
166
167 See also \fI\-\-unix\-socket\fP. Added in 7.53.0.
168-.IP "\-\-alt\-svc <file name>"
169-(HTTPS) This option enables the alt\-svc parser in curl. If the file name points to an
170-existing alt\-svc cache file, that gets used. After a completed transfer, the
171-cache is saved to the file name again if it has been modified.
172+.IP "\-\-alt\-svc <filename>"
173+(HTTPS) Enable the alt\-svc parser. If the filename points to an existing alt\-svc cache
174+file, that gets used. After a completed transfer, the cache is saved to the
175+filename again if it has been modified.
176
177-Specify a "" file name (zero length) to avoid loading/saving and make curl
178-just handle the cache in memory.
179+Specify a "" filename (zero length) to avoid loading/saving and make curl just
180+handle the cache in memory.
181
182 If this option is used several times, curl loads contents from all the
183 files but the last one is used for saving.
184@@ -312,10 +312,10 @@ Example:
185
186 See also \fI\-\-resolve\fP and \fI\-\-connect\-to\fP. Added in 7.64.1.
187 .IP "\-\-anyauth"
188-(HTTP) Tells curl to figure out authentication method by itself, and use the most
189-secure one the remote site claims to support. This is done by first doing a
190-request and checking the response\-headers, thus possibly inducing an extra
191-network round\-trip. This is used instead of setting a specific authentication
192+(HTTP) Figure out authentication method automatically, and use the most secure one
193+the remote site claims to support. This is done by first doing a request and
194+checking the response\-headers, thus possibly inducing an extra network
195+round\-trip. This option is used instead of setting a specific authentication
196 method, which you can do with \fI\-\-basic\fP, \fI\-\-digest\fP, \fI\-\-ntlm\fP, and \fI\-\-negotiate\fP.
197
198 Using \fI\-\-anyauth\fP is not recommended if you do uploads from stdin, since it may
199@@ -347,7 +347,7 @@ Example:
200 .fi
201
202 See also \fI-r, \-\-range\fP and \fI-C, \-\-continue\-at\fP.
203-.IP "\-\-aws\-sigv4 <provider1[:provider2[:region[:service]]]>"
204+.IP "\-\-aws\-sigv4 <provider1[:prvdr2[:reg[:srv]]]>"
205 (HTTP) Use AWS V4 signature authentication in the transfer.
206
207 The provider argument is a string that is used by the algorithm when creating
208@@ -369,8 +369,8 @@ Example:
209
210 See also \fI\-\-basic\fP and \fI-u, \-\-user\fP. Added in 7.75.0.
211 .IP "\-\-basic"
212-(HTTP) Tells curl to use HTTP Basic authentication with the remote host. This is the
213-default and this option is usually pointless, unless you use it to override a
214+(HTTP) Use HTTP Basic authentication with the remote host. This method is the default
215+and this option is usually pointless, unless you use it to override a
216 previously set option that sets a different authentication method (such as
217 \fI\-\-ntlm\fP, \fI\-\-digest\fP, or \fI\-\-negotiate\fP).
218
219@@ -385,10 +385,10 @@ Example:
220
221 See also \fI\-\-proxy\-basic\fP.
222 .IP "\-\-ca\-native"
223-(TLS) Tells curl to use the CA store from the native operating system to verify the
224-peer. By default, curl otherwise uses a CA store provided in a single file or
225-directory, but when using this option it interfaces the operating system\(aqs
226-own vault.
227+(TLS) Use the CA store from the native operating system to verify the peer. By
228+default, curl otherwise uses a CA store provided in a single file or
229+directory, but when using this option it interfaces the operating system\(aqs own
230+vault.
231
232 This option works for curl on Windows when built to use OpenSSL, wolfSSL
233 (added in 8.3.0) or GnuTLS (added in 8.5.0). When curl on Windows is built to
234@@ -405,10 +405,10 @@ Example:
235
236 See also \fI\-\-cacert\fP, \fI\-\-capath\fP and \fI-k, \-\-insecure\fP. Added in 8.2.0.
237 .IP "\-\-cacert <file>"
238-(TLS) Tells curl to use the specified certificate file to verify the peer. The file
239-may contain multiple CA certificates. The certificate(s) must be in PEM
240-format. Normally curl is built to use a default file for this, so this option
241-is typically used to alter that default file.
242+(TLS) Use the specified certificate file to verify the peer. The file may contain
243+multiple CA certificates. The certificate(s) must be in PEM format. Normally
244+curl is built to use a default file for this, so this option is typically used
245+to alter that default file.
246
247 curl recognizes the environment variable named \(aqCURL_CA_BUNDLE\(aq if it is set
248 and the TLS backend is not Schannel, and uses the given path as a path to a CA
249@@ -438,13 +438,13 @@ Example:
250
251 See also \fI\-\-capath\fP and \fI-k, \-\-insecure\fP.
252 .IP "\-\-capath <dir>"
253-(TLS) Tells curl to use the specified certificate directory to verify the
254-peer. Multiple paths can be provided by separating them with ":" (e.g.
255-\&"path1:path2:path3"). The certificates must be in PEM format, and if curl is
256-built against OpenSSL, the directory must have been processed using the
257-c_rehash utility supplied with OpenSSL. Using \fI\-\-capath\fP can allow
258-OpenSSL\-powered curl to make SSL\-connections much more efficiently than using
259-\fI\-\-cacert\fP if the \fI\-\-cacert\fP file contains many CA certificates.
260+(TLS) Use the specified certificate directory to verify the peer. Multiple paths can
261+be provided by separated with colon (":") (e.g. "path1:path2:path3"). The
262+certificates must be in PEM format, and if curl is built against OpenSSL, the
263+directory must have been processed using the c_rehash utility supplied with
264+OpenSSL. Using \fI\-\-capath\fP can allow OpenSSL\-powered curl to make SSL\-connections
265+much more efficiently than using \fI\-\-cacert\fP if the \fI\-\-cacert\fP file contains many
266+CA certificates.
267
268 If this option is set, the default capath value is ignored.
269
270@@ -457,14 +457,14 @@ Example:
271
272 See also \fI\-\-cacert\fP and \fI-k, \-\-insecure\fP.
273 .IP "\-\-cert\-status"
274-(TLS) Tells curl to verify the status of the server certificate by using the
275-Certificate Status Request (aka. OCSP stapling) TLS extension.
276+(TLS) Verify the status of the server certificate by using the Certificate Status
277+Request (aka. OCSP stapling) TLS extension.
278
279 If this option is enabled and the server sends an invalid (e.g. expired)
280 response, if the response suggests that the server certificate has been
281 revoked, or no response at all is received, the verification fails.
282
283-This is currently only implemented in the OpenSSL and GnuTLS backends.
284+This support is currently only implemented in the OpenSSL and GnuTLS backends.
285
286 Providing --cert-status multiple times has no extra effect.
287 Disable it again with \-\-no-cert-status.
288@@ -476,8 +476,8 @@ Example:
289
290 See also \fI\-\-pinnedpubkey\fP.
291 .IP "\-\-cert\-type <type>"
292-(TLS) Tells curl what type the provided client certificate is using. PEM, DER, ENG
293-and P12 are recognized types.
294+(TLS) Set type of the provided client certificate. PEM, DER, ENG and P12 are
295+recognized types.
296
297 The default type depends on the TLS backend and is usually PEM, however for
298 Secure Transport and Schannel it is P12. If \fI\-E, \-\-cert\fP is a pkcs11: URI then ENG is
299@@ -492,13 +492,13 @@ Example:
300
301 See also \fI-E, \-\-cert\fP, \fI\-\-key\fP and \fI\-\-key\-type\fP.
302 .IP "\-E, \-\-cert <certificate[:password]>"
303-(TLS) Tells curl to use the specified client certificate file when getting a file
304-with HTTPS, FTPS or another SSL\-based protocol. The certificate must be in
305-PKCS#12 format if using Secure Transport, or PEM format if using any other
306-engine. If the optional password is not specified, it is queried for on
307-the terminal. Note that this option assumes a certificate file that is the
308-private key and the client certificate concatenated. See \fI\-E, \-\-cert\fP and \fI\-\-key\fP to
309-specify them independently.
310+(TLS) Use the specified client certificate file when getting a file with HTTPS, FTPS
311+or another SSL\-based protocol. The certificate must be in PKCS#12 format if
312+using Secure Transport, or PEM format if using any other engine. If the
313+optional password is not specified, it is queried for on the terminal. Note
314+that this option assumes a certificate file that is the private key and the
315+client certificate concatenated. See \fI\-E, \-\-cert\fP and \fI\-\-key\fP to specify them
316+independently.
317
318 In the <certificate> portion of the argument, you must escape the character
319 \&":" as "\\:" so that it is not recognized as the password delimiter. Similarly,
320@@ -520,8 +520,8 @@ precede it with "./" prefix, in order to avoid confusion with a nickname.
321
322 (Schannel only) Client certificates must be specified by a path expression to
323 a certificate store. (Loading \fIPFX\fP is not supported; you can import it to a
324-store first). You can use "<store location>\\<store name>\\<thumbprint>" to
325-refer to a certificate in the system certificates store, for example,
326+store first). You can use "<store location>\\<store name>\\<thumbprint>"
327+to refer to a certificate in the system certificates store, for example,
328 \fI"CurrentUser\\MY\\934a7ac6f8a5d579285a74fa61e19f23ddfe8d7a"\fP. Thumbprint is
329 usually a SHA\-1 hex string which you can see in certificate details. Following
330 store locations are supported: \fICurrentUser\fP, \fILocalMachine\fP,
331@@ -551,8 +551,8 @@ Example:
332
333 See also \fI\-\-tlsv1.3\fP, \fI\-\-tls13\-ciphers\fP and \fI\-\-proxy\-ciphers\fP.
334 .IP "\-\-compressed\-ssh"
335-(SCP SFTP) Enables built\-in SSH compression.
336-This is a request, not an order; the server may or may not do it.
337+(SCP SFTP) Enables built\-in SSH compression. This is a request, not an order; the server
338+may or may not do it.
339
340 Providing --compressed-ssh multiple times has no extra effect.
341 Disable it again with \-\-no-compressed-ssh.
342@@ -597,9 +597,9 @@ is specified with one or two dashes, there can be no colon or equals character
343 between the option and its parameter.
344
345 If the parameter contains whitespace or starts with a colon (:) or equals sign
346-(=), it must be specified enclosed within double quotes ("). Within double
347-quotes the following escape sequences are available: \\\\, \\", \\t, \\n, \\r and
348-\\v. A backslash preceding any other letter is ignored.
349+(=), it must be specified enclosed within double quotes ("like this"). Within
350+double quotes the following escape sequences are available: \\\\, \\", \\t, \\n, \\r
351+and \\v. A backslash preceding any other letter is ignored.
352
353 If the first non\-blank column of a config line is a \(aq#\(aq character, that line
354 is treated as a comment.
355@@ -607,7 +607,8 @@ is treated as a comment.
356 Only write one option per physical line in the config file. A single line is
357 required to be no more than 10 megabytes (since 8.2.0).
358
359-Specify the filename to \fI\-K, \-\-config\fP as \(aq\-\(aq to make curl read the file from stdin.
360+Specify the filename to \fI\-K, \-\-config\fP as minus "\-" to make curl read the file from
361+stdin.
362
363 Note that to be able to specify a URL in the config file, you need to specify
364 it using the \fI\-\-url\fP option, and not by simply writing the URL on its own
365@@ -648,7 +649,7 @@ config file is checked for in the following places in this order:
366 7) Non\-Windows: use getpwuid to find the home directory
367
368 8) On Windows, if it finds no \fI.curlrc\fP file in the sequence described above, it
369-checks for one in the same dir the curl executable is placed.
370+checks for one in the same directory the curl executable is placed.
371
372 On Windows two filenames are checked per location: \fI.curlrc\fP and \fI_curlrc\fP,
373 preferring the former. Older versions on Windows checked for \fI_curlrc\fP only.
374@@ -661,7 +662,7 @@ Example:
375 .fi
376
377 See also \fI-q, \-\-disable\fP.
378-.IP "\-\-connect\-timeout <fractional seconds>"
379+.IP "\-\-connect\-timeout <seconds>"
380 Maximum time in seconds that you allow curl\(aqs connection to take. This only
381 limits the connection phase, so if curl connects within the given period it
382 continues \- if not it exits.
383@@ -683,14 +684,14 @@ Examples:
384
385 See also \fI-m, \-\-max\-time\fP.
386 .IP "\-\-connect\-to <HOST1:PORT1:HOST2:PORT2>"
387-For a request to the given "HOST1:PORT1" pair, connect to "HOST2:PORT2"
388-instead. This option is suitable to direct requests at a specific server,
389-e.g. at a specific cluster node in a cluster of servers. This option is only
390-used to establish the network connection. It does NOT affect the hostname/port
391-that is used for TLS/SSL (e.g. SNI, certificate verification) or for the
392-application protocols. "HOST1" and "PORT1" may be the empty string, meaning
393-\&"any host/port". "HOST2" and "PORT2" may also be the empty string, meaning
394-\&"use the request\(aqs original host/port".
395+For a request intended for the "HOST1:PORT1" pair, connect to "HOST2:PORT2"
396+instead. This option is only used to establish the network connection. It does
397+NOT affect the hostname/port number that is used for TLS/SSL (e.g. SNI,
398+certificate verification) or for the application protocols.
399+
400+\&"HOST1" and "PORT1" may be empty strings, meaning any host or any port number.
401+\&"HOST2" and "PORT2" may also be empty strings, meaning use the request\(aqs
402+original hostname and port number.
403
404 A hostname specified to this option is compared as a string, so it needs to
405 match the name used in request URL. It can be either numerical such as
406@@ -705,12 +706,12 @@ Example:
407
408 See also \fI\-\-resolve\fP and \fI-H, \-\-header\fP.
409 .IP "\-C, \-\-continue\-at <offset>"
410-Continue/Resume a previous file transfer at the given offset. The given offset
411-is the exact number of bytes that are skipped, counting from the beginning
412-of the source file before it is transferred to the destination. If used with
413-uploads, the FTP server command SIZE is not used by curl.
414+Resume a previous transfer from the given byte offset. The given offset is the
415+exact number of bytes that are skipped, counting from the beginning of the
416+source file before it is transferred to the destination. If used with uploads,
417+the FTP server command SIZE is not used by curl.
418
419-Use "\-C \-" to tell curl to automatically find out where/how to resume the
420+Use "\-C \-" to instruct curl to automatically find out where/how to resume the
421 transfer. It then uses the given output/input files to figure that out.
422
423 If --continue-at is provided several times, the last set value is used.
424@@ -725,9 +726,10 @@ See also \fI-r, \-\-range\fP.
425 .IP "\-c, \-\-cookie\-jar <filename>"
426 (HTTP) Specify to which file you want curl to write all cookies after a completed
427 operation. Curl writes all cookies from its in\-memory cookie storage to the
428-given file at the end of operations. If no cookies are known, no data is
429-written. The file is created using the Netscape cookie file format. If you set
430-the file name to a single dash, "\-", the cookies are written to stdout.
431+given file at the end of operations. Even if no cookies are known, a file is
432+created so that it removes any formerly existing cookies from the file. The
433+file uses the Netscape cookie file format. If you set the filename to a single
434+minus, "\-", the cookies are written to stdout.
435
436 The file specified with \fI\-c, \-\-cookie\-jar\fP is only used for output. No cookies are
437 read from the file. To read cookies, use the \fI\-b, \-\-cookie\fP option. Both options
438@@ -753,26 +755,28 @@ See also \fI-b, \-\-cookie\fP.
439 .IP "\-b, \-\-cookie <data|filename>"
440 (HTTP) Pass the data to the HTTP server in the Cookie header. It is supposedly the
441 data previously received from the server in a "Set\-Cookie:" line. The data
442-should be in the format "NAME1=VALUE1; NAME2=VALUE2". This makes curl use the
443+should be in the format "NAME1=VALUE1; NAME2=VALUE2" or as a single filename.
444+
445+When given a set of specific cookies and not a filename, it makes curl use the
446 cookie header with this content explicitly in all outgoing request(s). If
447 multiple requests are done due to authentication, followed redirects or
448-similar, they all get this cookie passed on.
449+similar, they all get this cookie header passed on.
450
451-If no \(aq=\(aq symbol is used in the argument, it is instead treated as a filename
452+If no "=" symbol is used in the argument, it is instead treated as a filename
453 to read previously stored cookie from. This option also activates the cookie
454 engine which makes curl record incoming cookies, which may be handy if you are
455 using this in combination with the \fI\-L, \-\-location\fP option or do multiple URL
456 transfers on the same invoke.
457
458-If the file name is exactly a minus ("\-"), curl instead reads the contents from
459-stdin. If the file name is an empty string ("") and is the only cookie input,
460-curl will activate the cookie engine without any cookies.
461+If the filename is a single minus ("\-"), curl reads the contents from stdin.
462+If the filename is an empty string ("") and is the only cookie input, curl
463+activates the cookie engine without any cookies.
464
465 The file format of the file to read cookies from should be plain HTTP headers
466 (Set\-Cookie style) or the Netscape/Mozilla cookie file format.
467
468 The file specified with \fI\-b, \-\-cookie\fP is only used as input. No cookies are written
469-to the file. To store cookies, use the \fI\-c, \-\-cookie\-jar\fP option.
470+to that file. To store cookies, use the \fI\-c, \-\-cookie\-jar\fP option.
471
472 If you use the Set\-Cookie file format and do not specify a domain then the
473 cookie is not sent since the domain never matches. To address this, set a
474@@ -795,6 +799,7 @@ Examples:
475 curl -b "" https://example.com
476 curl -b cookiefile https://example.com
477 curl -b cookiefile -c cookiefile https://example.com
478+ curl -b name=Jane https://example.com
479 .fi
480
481 See also \fI-c, \-\-cookie\-jar\fP and \fI-j, \-\-junk\-session\-cookies\fP.
482@@ -802,7 +807,7 @@ See also \fI-c, \-\-cookie\-jar\fP and \fI-j, \-\-junk\-session\-cookies\fP.
483 When used in conjunction with the \fI\-o, \-\-output\fP option, curl creates the necessary
484 local directory hierarchy as needed. This option creates the directories
485 mentioned with the \fI\-o, \-\-output\fP option combined with the path possibly set with
486-\fI\-\-output\-dir\fP. If the combined output file name uses no directory, or if the
487+\fI\-\-output\-dir\fP. If the combined output filename uses no directory, or if the
488 directories it mentions already exist, no directories are created.
489
490 Created directories are made with mode 0750 on unix style file systems.
491@@ -860,11 +865,11 @@ Example:
492 .fi
493
494 See also \fI\-\-cacert\fP and \fI\-\-capath\fP.
495-.IP "\-\-curves <algorithm list>"
496-(TLS) Tells curl to request specific curves to use during SSL session establishment
497-according to RFC 8422, 5.1. Multiple algorithms can be provided by separating
498-them with ":" (e.g. "X25519:P\-521"). The parameter is available identically in
499-the OpenSSL "s_client" and "s_server" utilities.
500+.IP "\-\-curves <list>"
501+(TLS) Set specific curves to use during SSL session establishment according to RFC
502+8422, 5.1. Multiple algorithms can be provided by separating them with ":"
503+(e.g. "X25519:P\-521"). The parameter is available identically in the OpenSSL
504+\&"s_client" and "s_server" utilities.
505
506 \fI\-\-curves\fP allows a OpenSSL powered curl to make SSL\-connections with exactly
507 the (EC) curve requested by the client, avoiding nontransparent client/server
508@@ -881,7 +886,7 @@ Example:
509
510 See also \fI\-\-ciphers\fP. Added in 7.73.0.
511 .IP "\-\-data\-ascii <data>"
512-(HTTP) This is just an alias for \fI\-d, \-\-data\fP.
513+(HTTP) This option is just an alias for \fI\-d, \-\-data\fP.
514
515 --data-ascii can be used several times in a command line
516
517@@ -892,7 +897,7 @@ Example:
518
519 See also \fI\-\-data\-binary\fP, \fI\-\-data\-raw\fP and \fI\-\-data\-urlencode\fP.
520 .IP "\-\-data\-binary <data>"
521-(HTTP) This posts data exactly as specified with no extra processing whatsoever.
522+(HTTP) Post data exactly as specified with no extra processing whatsoever.
523
524 If you start the data with the letter @, the rest should be a filename. Data
525 is posted in a similar manner as \fI\-d, \-\-data\fP does, except that newlines and
526@@ -915,8 +920,8 @@ Example:
527
528 See also \fI\-\-data\-ascii\fP.
529 .IP "\-\-data\-raw <data>"
530-(HTTP) This posts data similarly to \fI\-d, \-\-data\fP but without the special
531-interpretation of the @ character.
532+(HTTP) Post data similarly to \fI\-d, \-\-data\fP but without the special interpretation of the @
533+character.
534
535 --data-raw can be used several times in a command line
536
537@@ -928,31 +933,31 @@ Examples:
538
539 See also \fI-d, \-\-data\fP.
540 .IP "\-\-data\-urlencode <data>"
541-(HTTP) This posts data, similar to the other \fI\-d, \-\-data\fP options with the exception
542-that this performs URL\-encoding.
543+(HTTP) Post data, similar to the other \fI\-d, \-\-data\fP options with the exception that this
544+performs URL\-encoding.
545
546-To be CGI\-compliant, the <data> part should begin with a \fIname\fP followed
547-by a separator and a content specification. The <data> part can be passed to
548+To be CGI\-compliant, the <data> part should begin with a \fIname\fP followed by
549+a separator and a content specification. The <data> part can be passed to
550 curl using one of the following syntaxes:
551 .RS
552 .IP content
553-This makes curl URL\-encode the content and pass that on. Just be careful
554-so that the content does not contain any = or @ symbols, as that makes
555-the syntax match one of the other cases below!
556+URL\-encode the content and pass that on. Just be careful so that the content
557+does not contain any "=" or "@" symbols, as that makes the syntax match one of
558+the other cases below!
559 .IP =content
560-This makes curl URL\-encode the content and pass that on. The preceding =
561-symbol is not included in the data.
562+URL\-encode the content and pass that on. The preceding "=" symbol is not
563+included in the data.
564 .IP name=content
565-This makes curl URL\-encode the content part and pass that on. Note that
566-the name part is expected to be URL\-encoded already.
567+URL\-encode the content part and pass that on. Note that the name part is
568+expected to be URL\-encoded already.
569 .IP @filename
570-This makes curl load data from the given file (including any newlines),
571-URL\-encode that data and pass it on in the POST.
572+load data from the given file (including any newlines), URL\-encode that data
573+and pass it on in the POST.
574 .IP name@filename
575-This makes curl load data from the given file (including any newlines),
576-URL\-encode that data and pass it on in the POST. The name part gets an equal
577-sign appended, resulting in \fIname=urlencoded\-file\-content\fP. Note that the
578-name is expected to be URL\-encoded already.
579+load data from the given file (including any newlines), URL\-encode that data
580+and pass it on in the POST. The name part gets an equal sign appended,
581+resulting in \fIname=urlencoded\-file\-content\fP. Note that the name is expected to
582+be URL\-encoded already.
583 .RE
584 .IP
585
586@@ -970,7 +975,7 @@ See also \fI-d, \-\-data\fP and \fI\-\-data\-raw\fP.
587 .IP "\-d, \-\-data <data>"
588 (HTTP MQTT) Sends the specified data in a POST request to the HTTP server, in the same way
589 that a browser does when a user has filled in an HTML form and presses the
590-submit button. This makes curl pass the data to the server using the
591+submit button. This option makes curl pass the data to the server using the
592 content\-type application/x\-www\-form\-urlencoded. Compare to \fI\-F, \-\-form\fP.
593
594 \fI\-\-data\-raw\fP is almost the same but does not have a special interpretation of
595@@ -983,11 +988,11 @@ data pieces specified are merged with a separating &\-symbol. Thus, using
596 \(aq\-d name=daniel \-d skill=lousy\(aq would generate a post chunk that looks like
597 \(aqname=daniel&skill=lousy\(aq.
598
599-If you start the data with the letter @, the rest should be a file name to
600-read the data from, or \- if you want curl to read the data from stdin. Posting
601-data from a file named \(aqfoobar\(aq would thus be done with \fI\-d, \-\-data\fP @foobar. When
602-\fI\-d, \-\-data\fP is told to read from a file like that, carriage returns and newlines
603-are stripped out. If you do not want the @ character to have a special
604+If you start the data with the letter @, the rest should be a filename to read
605+the data from, or \- if you want curl to read the data from stdin. Posting data
606+from a file named \(aqfoobar\(aq would thus be done with \fI\-d, \-\-data\fP @foobar. When \fI\-d, \-\-data\fP
607+is told to read from a file like that, carriage returns, newlines and null
608+bytes are stripped out. If you do not want the @ character to have a special
609 interpretation use \fI\-\-data\-raw\fP instead.
610
611 The data for this option is passed on to the server exactly as provided on the
612@@ -1005,8 +1010,7 @@ Examples:
613
614 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.
615 .IP "\-\-delegation <LEVEL>"
616-(GSS/kerberos) Set LEVEL to tell the server what it is allowed to delegate when it
617-comes to user credentials.
618+(GSS/kerberos) Set LEVEL what curl is allowed to delegate when it comes to user credentials.
619 .RS
620 .IP none
621 Do not allow any delegation.
622@@ -1027,9 +1031,9 @@ Example:
623
624 See also \fI-k, \-\-insecure\fP and \fI\-\-ssl\fP.
625 .IP "\-\-digest"
626-(HTTP) Enables HTTP Digest authentication. This is an authentication scheme that
627-prevents the password from being sent over the wire in clear text. Use this in
628-combination with the normal \fI\-u, \-\-user\fP option to set user name and password.
629+(HTTP) Enables HTTP Digest authentication. This authentication scheme avoids sending
630+the password over the wire in clear text. Use this in combination with the
631+normal \fI\-u, \-\-user\fP option to set username and password.
632
633 Providing --digest multiple times has no extra effect.
634 Disable it again with \-\-no-digest.
635@@ -1041,13 +1045,13 @@ Example:
636
637 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.
638 .IP "\-\-disable\-eprt"
639-(FTP) Tell curl to disable the use of the EPRT and LPRT commands when doing active
640-FTP transfers. Curl normally first attempts to use EPRT before using PORT, but
641-with this option, it uses PORT right away. EPRT is an extension to the
642-original FTP protocol, and does not work on all servers, but enables more
643-functionality in a better way than the traditional PORT command.
644+(FTP) Disable the use of the EPRT and LPRT commands when doing active FTP transfers.
645+Curl normally first attempts to use EPRT before using PORT, but with this
646+option, it uses PORT right away. EPRT is an extension to the original FTP
647+protocol, and does not work on all servers, but enables more functionality in
648+a better way than the traditional PORT command.
649
650--\-eprt can be used to explicitly enable EPRT again and \--no\-eprt is an alias
651+\fI\-\-eprt\fP can be used to explicitly enable EPRT again and \fI\-\-no\-eprt\fP is an alias
652 for \fI\-\-disable\-eprt\fP.
653
654 If the server is accessed using IPv6, this option has no effect as EPRT is
655@@ -1066,11 +1070,11 @@ Example:
656
657 See also \fI\-\-disable\-epsv\fP and \fI-P, \-\-ftp\-port\fP.
658 .IP "\-\-disable\-epsv"
659-(FTP) Tell curl to disable the use of the EPSV command when doing passive FTP
660-transfers. Curl normally first attempts to use EPSV before PASV, but with this
661-option, it does not try EPSV.
662+(FTP) Disable the use of the EPSV command when doing passive FTP transfers. Curl
663+normally first attempts to use EPSV before PASV, but with this option, it does
664+not try EPSV.
665
666--\-epsv can be used to explicitly enable EPSV again and \--no\-epsv is an alias
667+\fI\-\-epsv\fP can be used to explicitly enable EPSV again and \fI\-\-no\-epsv\fP is an alias
668 for \fI\-\-disable\-epsv\fP.
669
670 If the server is an IPv6 host, this option has no effect as EPSV is necessary
671@@ -1106,8 +1110,8 @@ Example:
672
673 See also \fI-K, \-\-config\fP.
674 .IP "\-\-disallow\-username\-in\-url"
675-This tells curl to exit if passed a URL containing a username. This is probably
676-most useful when the URL is being provided at runtime or similar.
677+Exit with error if passed a URL containing a username. Probably most useful
678+when the URL is being provided at runtime or similar.
679
680 Providing --disallow-username-in-url multiple times has no extra effect.
681 Disable it again with \-\-no-disallow-username-in-url.
682@@ -1119,7 +1123,7 @@ Example:
683
684 See also \fI\-\-proto\fP. Added in 7.61.0.
685 .IP "\-\-dns\-interface <interface>"
686-(DNS) Tell curl to send outgoing DNS requests through <interface>. This option is a
687+(DNS) Send outgoing DNS requests through the given interface. This option is a
688 counterpart to \fI\-\-interface\fP (which does not affect DNS). The supplied string
689 must be an interface name (not an address).
690
691@@ -1132,9 +1136,9 @@ Example:
692
693 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.
694 .IP "\-\-dns\-ipv4\-addr <address>"
695-(DNS) Tell curl to bind to a specific IP address when making IPv4 DNS requests, so
696-that the DNS requests originate from this address. The argument should be a
697-single IPv4 address.
698+(DNS) Bind to a specific IP address when making IPv4 DNS requests, so that the DNS
699+requests originate from this address. The argument should be a single IPv4
700+address.
701
702 If --dns-ipv4-addr is provided several times, the last set value is used.
703
704@@ -1145,9 +1149,9 @@ Example:
705
706 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.
707 .IP "\-\-dns\-ipv6\-addr <address>"
708-(DNS) Tell curl to bind to a specific IP address when making IPv6 DNS requests, so
709-that the DNS requests originate from this address. The argument should be a
710-single IPv6 address.
711+(DNS) Bind to a specific IP address when making IPv6 DNS requests, so that the DNS
712+requests originate from this address. The argument should be a single IPv6
713+address.
714
715 If --dns-ipv6-addr is provided several times, the last set value is used.
716
717@@ -1158,22 +1162,31 @@ Example:
718
719 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.
720 .IP "\-\-dns\-servers <addresses>"
721-(DNS) Set the list of DNS servers to be used instead of the system default.
722-The list of IP addresses should be separated with commas. Port numbers
723-may also optionally be given as \fI:<port\-number>\fP after each IP
724-address.
725+(DNS) Set the list of DNS servers to be used instead of the system default. The list
726+of IP addresses should be separated with commas. Port numbers may also
727+optionally be given, appended to the IP address separated with a colon.
728
729 If --dns-servers is provided several times, the last set value is used.
730
731-Example:
732+Examples:
733 .nf
734 curl --dns-servers 192.168.0.1,192.168.0.2 https://example.com
735+ curl --dns-servers 10.0.0.1:53 https://example.com
736 .fi
737
738 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.
739 .IP "\-\-doh\-cert\-status"
740 Same as \fI\-\-cert\-status\fP but used for DoH (DNS\-over\-HTTPS).
741
742+Verifies the status of the DoH servers\(aq certificate by using the Certificate
743+Status Request (aka. OCSP stapling) TLS extension.
744+
745+If this option is enabled and the DoH server sends an invalid (e.g. expired)
746+response, if the response suggests that the server certificate has been
747+revoked, or no response at all is received, the verification fails.
748+
749+This support is currently only implemented in the OpenSSL and GnuTLS backends.
750+
751 Providing --doh-cert-status multiple times has no extra effect.
752 Disable it again with \-\-no-doh-cert-status.
753
754@@ -1262,17 +1275,14 @@ Example:
755
756 See also \fI\-\-ciphers\fP and \fI\-\-curves\fP.
757 .IP "\-\-etag\-compare <file>"
758-(HTTP) This option makes a conditional HTTP request for the specific ETag read
759-from the given file by sending a custom If\-None\-Match header using the
760-stored ETag.
761+(HTTP) Make a conditional HTTP request for the specific ETag read from the given file
762+by sending a custom If\-None\-Match header using the stored ETag.
763
764-For correct results, make sure that the specified file contains only a
765-single line with the desired ETag. An empty file is parsed as an empty
766-ETag.
767+For correct results, make sure that the specified file contains only a single
768+line with the desired ETag. An empty file is parsed as an empty ETag.
769
770-Use the option \fI\-\-etag\-save\fP to first save the ETag from a response, and
771-then use this option to compare against the saved ETag in a subsequent
772-request.
773+Use the option \fI\-\-etag\-save\fP to first save the ETag from a response, and then
774+use this option to compare against the saved ETag in a subsequent request.
775
776 If --etag-compare is provided several times, the last set value is used.
777
778@@ -1283,8 +1293,8 @@ Example:
779
780 See also \fI\-\-etag\-save\fP and \fI-z, \-\-time\-cond\fP. Added in 7.68.0.
781 .IP "\-\-etag\-save <file>"
782-(HTTP) This option saves an HTTP ETag to the specified file. An ETag is a
783-caching related header, usually returned in a response.
784+(HTTP) Save an HTTP ETag to the specified file. An ETag is a caching related header,
785+usually returned in a response.
786
787 If no ETag is sent by the server, an empty file is created.
788
789@@ -1299,11 +1309,11 @@ See also \fI\-\-etag\-compare\fP. Added in 7.68.0.
790 .IP "\-\-expect100\-timeout <seconds>"
791 (HTTP) Maximum time in seconds that you allow curl to wait for a 100\-continue
792 response when curl emits an Expects: 100\-continue header in its request. By
793-default curl waits one second. This option accepts decimal values! When
794-curl stops waiting, it continues as if the response has been received.
795+default curl waits one second. This option accepts decimal values. When curl
796+stops waiting, it continues as if a response was received.
797
798-The decimal value needs to provided using a dot (.) as decimal separator \- not
799-the local version even if it might be using another separator.
800+The decimal value needs to provided using a dot (".") as decimal separator \-
801+not the local version even if it might be using another separator.
802
803 If --expect100-timeout is provided several times, the last set value is used.
804
805@@ -1319,7 +1329,7 @@ Fail and exit on the first detected transfer error.
806 When curl is used to do multiple transfers on the command line, it attempts to
807 operate on each given URL, one by one. By default, it ignores errors if there
808 are more URLs given and the last URL\(aqs success determines the error code curl
809-returns. So early failures are "hidden" by subsequent successful transfers.
810+returns. Early failures are "hidden" by subsequent successful transfers.
811
812 Using this option, curl instead returns an error on the first transfer that
813 fails, independent of the amount of URLs that are given on the command
814@@ -1343,9 +1353,9 @@ See also \fI-f, \-\-fail\fP and \fI\-\-fail\-with\-body\fP. Added in 7.52.0.
815 .IP "\-\-fail\-with\-body"
816 (HTTP) Return an error on server errors where the HTTP response code is 400 or
817 greater). In normal cases when an HTTP server fails to deliver a document, it
818-returns an HTML document stating so (which often also describes why and
819-more). This flag allows curl to output and save that content but also to
820-return error 22.
821+returns an HTML document stating so (which often also describes why and more).
822+This option allows curl to output and save that content but also to return
823+error 22.
824
825 This is an alternative option to \fI\-f, \-\-fail\fP which makes curl fail for the same
826 circumstances but without saving the content.
827@@ -1363,8 +1373,8 @@ See also \fI-f, \-\-fail\fP and \fI\-\-fail\-early\fP. This option is mutually e
828 (HTTP) Fail fast with no output at all on server errors. This is useful to enable
829 scripts and users to better deal with failed attempts. In normal cases when an
830 HTTP server fails to deliver a document, it returns an HTML document stating
831-so (which often also describes why and more). This flag prevents curl from
832-outputting that and return error 22.
833+so (which often also describes why and more). This command line option
834+prevents curl from outputting that and return error 22.
835
836 This method is not fail\-safe and there are occasions where non\-successful
837 response codes slip through, especially when authentication is involved
838@@ -1380,13 +1390,12 @@ Example:
839
840 See also \fI\-\-fail\-with\-body\fP and \fI\-\-fail\-early\fP. This option is mutually exclusive to \fI\-\-fail\-with\-body\fP.
841 .IP "\-\-false\-start"
842-(TLS) Tells curl to use false start during the TLS handshake. False start is a mode
843-where a TLS client starts sending application data before verifying the
844-server\(aqs Finished message, thus saving a round trip when performing a full
845-handshake.
846+(TLS) Use false start during the TLS handshake. False start is a mode where a TLS
847+client starts sending application data before verifying the server\(aqs Finished
848+message, thus saving a round trip when performing a full handshake.
849
850-This is currently only implemented in the Secure Transport (on iOS 7.0 or
851-later, or OS X 10.9 or later) backend.
852+This functionality is currently only implemented in the Secure Transport (on
853+iOS 7.0 or later, or OS X 10.9 or later) backend.
854
855 Providing --false-start multiple times has no extra effect.
856 Disable it again with \-\-no-false-start.
857@@ -1398,8 +1407,8 @@ Example:
858
859 See also \fI\-\-tcp\-fastopen\fP.
860 .IP "\-\-form\-escape"
861-(HTTP) Tells curl to pass on names of multipart form fields and files using
862-backslash\-escaping instead of percent\-encoding.
863+(HTTP) Pass on names of multipart form fields and files using backslash\-escaping
864+instead of percent\-encoding.
865
866 If --form-escape is provided several times, the last set value is used.
867
868@@ -1411,39 +1420,39 @@ Example:
869 See also \fI-F, \-\-form\fP. Added in 7.81.0.
870 .IP "\-\-form\-string <name=string>"
871 (HTTP SMTP IMAP) Similar to \fI\-F, \-\-form\fP except that the value string for the named parameter is used
872-literally. Leading \(aq@\(aq and \(aq<\(aq characters, and the \(aq;type=\(aq string in
873-the value have no special meaning. Use this in preference to \fI\-F, \-\-form\fP if
874-there is any possibility that the string value may accidentally trigger the
875-\(aq@\(aq or \(aq<\(aq features of \fI\-F, \-\-form\fP.
876+literally. Leading @ and < characters, and the ";type=" string in the value
877+have no special meaning. Use this in preference to \fI\-F, \-\-form\fP if there is any
878+possibility that the string value may accidentally trigger the @ or <
879+features of \fI\-F, \-\-form\fP.
880
881 --form-string can be used several times in a command line
882
883 Example:
884 .nf
885- curl --form-string "data" https://example.com
886+ curl --form-string "name=data" https://example.com
887 .fi
888
889 See also \fI-F, \-\-form\fP.
890 .IP "\-F, \-\-form <name=content>"
891-(HTTP SMTP IMAP) For HTTP protocol family, this lets curl emulate a filled\-in form in which a
892-user has pressed the submit button. This causes curl to POST data using the
893-Content\-Type multipart/form\-data according to RFC 2388.
894+(HTTP SMTP IMAP) For the HTTP protocol family, emulate a filled\-in form in which a user has
895+pressed the submit button. This makes curl POST data using the Content\-Type
896+multipart/form\-data according to RFC 2388.
897
898-For SMTP and IMAP protocols, this is the means to compose a multipart mail
899-message to transmit.
900+For SMTP and IMAP protocols, this composes a multipart mail message to
901+transmit.
902
903 This enables uploading of binary files etc. To force the \(aqcontent\(aq part to be
904-a file, prefix the file name with an @ sign. To just get the content part from
905-a file, prefix the file name with the symbol <. The difference between @ and <
906-is then that @ makes a file get attached in the post as a file upload, while
907-the < makes a text field and just get the contents for that text field from a
908-file.
909-
910-Tell curl to read content from stdin instead of a file by using \- as
911-filename. This goes for both @ and < constructs. When stdin is used, the
912-contents is buffered in memory first by curl to determine its size and allow a
913-possible resend. Defining a part\(aqs data from a named non\-regular file (such as
914-a named pipe or similar) is not subject to buffering and is instead read at
915+a file, prefix the filename with an @ sign. To just get the content part from
916+a file, prefix the filename with the symbol <. The difference between @ and
917+< is then that @ makes a file get attached in the post as a file upload,
918+while the < makes a text field and just get the contents for that text field
919+from a file.
920+
921+Read content from stdin instead of a file by using a single "\-" as filename.
922+This goes for both @ and < constructs. When stdin is used, the contents is
923+buffered in memory first by curl to determine its size and allow a possible
924+resend. Defining a part\(aqs data from a named non\-regular file (such as a named
925+pipe or similar) is not subject to buffering and is instead read at
926 transmission time; since the full size is unknown before the transfer starts,
927 such data is sent as chunks by HTTP and rejected by IMAP.
928
929@@ -1467,8 +1476,8 @@ text field, but get the contents for it from a local file:
930 curl \-F "story=<hugefile.txt" https://example.com/
931 .fi
932
933-You can also tell curl what Content\-Type to use by using \(aqtype=\(aq, in a manner
934-similar to:
935+You can also instruct curl what Content\-Type to use by using "type=", in a
936+manner similar to:
937 .nf
938
939 curl \-F "web=@index.html;type=text/html" example.com
940@@ -1583,7 +1592,7 @@ Example:
941
942 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.
943 .IP "\-\-ftp\-account <data>"
944-(FTP) When an FTP server asks for "account data" after user name and password has
945+(FTP) When an FTP server asks for "account data" after username and password has
946 been provided, this data is sent off using the ACCT command.
947
948 If --ftp-account is provided several times, the last set value is used.
949@@ -1627,16 +1636,16 @@ See also \fI\-\-create\-dirs\fP.
950 server. The method argument should be one of the following alternatives:
951 .RS
952 .IP multicwd
953-curl does a single CWD operation for each path part in the given URL. For deep
954-hierarchies this means many commands. This is how RFC 1738 says it should
955-be done. This is the default but the slowest behavior.
956+Do a single CWD operation for each path part in the given URL. For deep
957+hierarchies this means many commands. This is how RFC 1738 says it should be
958+done. This is the default but the slowest behavior.
959 .IP nocwd
960-curl does no CWD at all. curl does SIZE, RETR, STOR etc and give a full
961-path to the server for all these commands. This is the fastest behavior.
962+Do no CWD at all. curl does SIZE, RETR, STOR etc and gives the full path to
963+the server for each of these commands. This is the fastest behavior.
964 .IP singlecwd
965-curl does one CWD with the full target directory and then operates on the file
966+Do one CWD with the full target directory and then operate on the file
967 \&"normally" (like in the multicwd case). This is somewhat more standards
968-compliant than \(aqnocwd\(aq but without the full penalty of \(aqmulticwd\(aq.
969+compliant than "nocwd" but without the full penalty of "multicwd".
970 .RE
971 .IP
972
973@@ -1672,16 +1681,16 @@ Example:
974 See also \fI\-\-disable\-epsv\fP.
975 .IP "\-P, \-\-ftp\-port <address>"
976 (FTP) Reverses the default initiator/listener roles when connecting with FTP. This
977-option makes curl use active mode. curl then tells the server to connect back
978-to the client\(aqs specified address and port, while passive mode asks the server
979-to setup an IP address and port for it to connect to. <address> should be one
980-of:
981+option makes curl use active mode. curl then commands the server to connect
982+back to the client\(aqs specified address and port, while passive mode asks the
983+server to setup an IP address and port for it to connect to. <address>
984+should be one of:
985 .RS
986 .IP interface
987 e.g. \fBeth0\fP to specify which interface\(aqs IP address you want to use (Unix only)
988 .IP "IP address"
989 e.g. \fB192.168.10.1\fP to specify the exact IP address
990-.IP "host name"
991+.IP hostname
992 e.g. \fBmy.host.domain\fP to specify the machine
993 .IP -
994 make curl pick the same IP address that is already used for the control
995@@ -1696,8 +1705,6 @@ curl what TCP port range to use. That means you specify a port range, from a
996 lower to a higher number. A single number works as well, but do note that it
997 increases the risk of failure since the port may not be available.
998
999-.RE
1000-.IP
1001
1002 If --ftp-port is provided several times, the last set value is used.
1003
1004@@ -1710,9 +1717,9 @@ Examples:
1005
1006 See also \fI\-\-ftp\-pasv\fP and \fI\-\-disable\-eprt\fP.
1007 .IP "\-\-ftp\-pret"
1008-(FTP) Tell curl to send a PRET command before PASV (and EPSV). Certain FTP servers,
1009-mainly drftpd, require this non\-standard command for directory listings as
1010-well as up and downloads in PASV mode.
1011+(FTP) Send a PRET command before PASV (and EPSV). Certain FTP servers, mainly
1012+drftpd, require this non\-standard command for directory listings as well as up
1013+and downloads in PASV mode.
1014
1015 Providing --ftp-pret multiple times has no extra effect.
1016 Disable it again with \-\-no-ftp-pret.
1017@@ -1724,9 +1731,9 @@ Example:
1018
1019 See also \fI-P, \-\-ftp\-port\fP and \fI\-\-ftp\-pasv\fP.
1020 .IP "\-\-ftp\-skip\-pasv\-ip"
1021-(FTP) Tell curl to not use the IP address the server suggests in its response to
1022-curl\(aqs PASV command when curl connects the data connection. Instead curl
1023-reuses the same IP address it already uses for the control connection.
1024+(FTP) Do not use the IP address the server suggests in its response to curl\(aqs PASV
1025+command when curl connects the data connection. Instead curl reuses the same
1026+IP address it already uses for the control connection.
1027
1028 This option is enabled by default (added in 7.74.0).
1029
1030@@ -1806,8 +1813,8 @@ Examples:
1031
1032 See also \fI-d, \-\-data\fP and \fI-X, \-\-request\fP.
1033 .IP "\-g, \-\-globoff"
1034-This option switches off the "URL globbing parser". When you set this option,
1035-you can specify URLs that contain the letters {}[] without having curl itself
1036+Switch off the URL globbing function. When you set this option, you can
1037+specify URLs that contain the letters {}[] without having curl itself
1038 interpret them. Note that these letters are not normal legal URL contents but
1039 they should be encoded according to the URI standard.
1040
1041@@ -1820,7 +1827,7 @@ Example:
1042 .fi
1043
1044 See also \fI-K, \-\-config\fP and \fI-q, \-\-disable\fP.
1045-.IP "\-\-happy\-eyeballs\-timeout\-ms <milliseconds>"
1046+.IP "\-\-happy\-eyeballs\-timeout\-ms <ms>"
1047 Happy Eyeballs is an algorithm that attempts to connect to both IPv4 and IPv6
1048 addresses for dual\-stack hosts, giving IPv6 a head\-start of the specified
1049 number of milliseconds. If the IPv6 address cannot be connected to within that
1050@@ -1840,7 +1847,7 @@ Example:
1051 .fi
1052
1053 See also \fI-m, \-\-max\-time\fP and \fI\-\-connect\-timeout\fP. Added in 7.59.0.
1054-.IP "\-\-haproxy\-clientip <IP address>"
1055+.IP "\-\-haproxy\-clientip <ip>"
1056 (HTTP) Sets a client IP in HAProxy PROXY protocol v1 header at the beginning of the
1057 connection.
1058
1059@@ -1866,9 +1873,9 @@ Example:
1060
1061 See also \fI-x, \-\-proxy\fP. Added in 8.2.0.
1062 .IP "\-\-haproxy\-protocol"
1063-(HTTP) Send a HAProxy PROXY protocol v1 header at the beginning of the
1064-connection. This is used by some load balancers and reverse proxies to
1065-indicate the client\(aqs true IP address and port.
1066+(HTTP) Send a HAProxy PROXY protocol v1 header at the beginning of the connection.
1067+This is used by some load balancers and reverse proxies to indicate the
1068+client\(aqs true IP address and port.
1069
1070 This option is primarily useful when sending test requests to a service that
1071 expects this header.
1072@@ -1911,7 +1918,7 @@ allows you to make even trickier stuff than curl would normally do. You should
1073 not replace internally set headers without knowing perfectly well what you are
1074 doing. Remove an internal header by giving a replacement without content on
1075 the right side of the colon, as in: \-H "Host:". If you send the custom header
1076-with no\-value then its header must be terminated with a semicolon, such as \\-H
1077+with no\-value then its header must be terminated with a semicolon, such as \-H
1078 \&"X\-Custom\-Header;" to send "X\-Custom\-Header:".
1079
1080 curl makes sure that each header you add/replace is sent with the proper
1081@@ -1951,10 +1958,9 @@ Examples:
1082
1083 See also \fI-A, \-\-user\-agent\fP and \fI-e, \-\-referer\fP.
1084 .IP "\-h, \-\-help <category>"
1085-Usage help. This lists all curl command line options within the given
1086-\fBcategory\fP.
1087+Usage help. List all curl command line options within the given \fBcategory\fP.
1088
1089-If no argument is provided, curl displays only the most important command line
1090+If no argument is provided, curl displays the most important command line
1091 arguments.
1092
1093 For category \fBall\fP, curl displays help for all options.
1094@@ -1995,18 +2001,18 @@ Example:
1095 .fi
1096
1097 See also \fI\-\-hostpubmd5\fP. Added in 7.80.0.
1098-.IP "\-\-hsts <file name>"
1099-(HTTPS) This option enables HSTS for the transfer. If the file name points to an
1100-existing HSTS cache file, that is used. After a completed transfer, the
1101-cache is saved to the file name again if it has been modified.
1102-
1103-If curl is told to use HTTP:// for a transfer involving a host name that
1104-exists in the HSTS cache, it upgrades the transfer to use HTTPS. Each HSTS
1105-cache entry has an individual life time after which the upgrade is no longer
1106+.IP "\-\-hsts <filename>"
1107+(HTTPS) Enable HSTS for the transfer. If the filename points to an existing HSTS cache
1108+file, that is used. After a completed transfer, the cache is saved to the
1109+filename again if it has been modified.
1110+
1111+If curl is told to use HTTP:// for a transfer involving a hostname that exists
1112+in the HSTS cache, it upgrades the transfer to use HTTPS. Each HSTS cache
1113+entry has an individual life time after which the upgrade is no longer
1114 performed.
1115
1116-Specify a "" file name (zero length) to avoid loading/saving and make curl
1117-just handle HSTS in memory.
1118+Specify a "" filename (zero length) to avoid loading/saving and make curl just
1119+handle HSTS in memory.
1120
1121 If this option is used several times, curl loads contents from all the
1122 files but the last one is used for saving.
1123@@ -2020,7 +2026,7 @@ Example:
1124
1125 See also \fI\-\-proto\fP. Added in 7.74.0.
1126 .IP "\-\-http0.9"
1127-(HTTP) Tells curl to be fine with HTTP version 0.9 response.
1128+(HTTP) Accept an HTTP version 0.9 response.
1129
1130 HTTP/0.9 is a response without headers and therefore you can also connect with
1131 this to non\-HTTP servers and still get a response since curl simply
1132@@ -2038,8 +2044,7 @@ Example:
1133
1134 See also \fI\-\-http1.1\fP, \fI\-\-http2\fP and \fI\-\-http3\fP. Added in 7.64.0.
1135 .IP "\-0, \-\-http1.0"
1136-(HTTP) Tells curl to use HTTP version 1.0 instead of using its internally preferred
1137-HTTP version.
1138+(HTTP) Use HTTP version 1.0 instead of using its internally preferred HTTP version.
1139
1140 Providing --http1.0 multiple times has no extra effect.
1141
1142@@ -2050,7 +2055,7 @@ Example:
1143
1144 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.
1145 .IP "\-\-http1.1"
1146-(HTTP) Tells curl to use HTTP version 1.1.
1147+(HTTP) Use HTTP version 1.1. This is the default with HTTP:// URLs.
1148
1149 Providing --http1.1 multiple times has no extra effect.
1150
1151@@ -2059,11 +2064,11 @@ Example:
1152 curl --http1.1 https://example.com
1153 .fi
1154
1155-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.
1156+See also \fI\-\-http1.0\fP and \fI\-\-http0.9\fP. This option is mutually exclusive to \fI\-\-http1.0\fP and \fI\-\-http2\fP and \fI\-\-http2\-prior\-knowledge\fP and \fI\-\-http3\fP.
1157 .IP "\-\-http2\-prior\-knowledge"
1158-(HTTP) Tells curl to issue its non\-TLS HTTP requests using HTTP/2 without HTTP/1.1
1159-Upgrade. It requires prior knowledge that the server supports HTTP/2 straight
1160-away. HTTPS requests still do HTTP/2 the standard way with negotiated protocol
1161+(HTTP) Issue a non\-TLS HTTP requests using HTTP/2 directly without HTTP/1.1 Upgrade.
1162+It requires prior knowledge that the server supports HTTP/2 straight away.
1163+HTTPS requests still do HTTP/2 the standard way with negotiated protocol
1164 version in the TLS handshake.
1165
1166 Providing --http2-prior-knowledge multiple times has no extra effect.
1167@@ -2074,9 +2079,9 @@ Example:
1168 curl --http2-prior-knowledge https://example.com
1169 .fi
1170
1171-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.
1172+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\-\-http1.0\fP and \fI\-\-http2\fP and \fI\-\-http3\fP.
1173 .IP "\-\-http2"
1174-(HTTP) Tells curl to use HTTP version 2.
1175+(HTTP) Use HTTP/2.
1176
1177 For HTTPS, this means curl negotiates HTTP/2 in the TLS handshake. curl does
1178 this by default.
1179@@ -2095,7 +2100,7 @@ Example:
1180 curl --http2 https://example.com
1181 .fi
1182
1183-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.
1184+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\-\-http1.0\fP and \fI\-\-http2\-prior\-knowledge\fP and \fI\-\-http3\fP.
1185 .IP "\-\-http3\-only"
1186 (HTTP) Instructs curl to use HTTP/3 to the host in the URL, with no fallback to
1187 earlier HTTP versions. HTTP/3 can only be used for HTTPS and not for HTTP
1188@@ -2115,11 +2120,11 @@ Example:
1189 curl --http3-only https://example.com
1190 .fi
1191
1192-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.
1193+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\-\-http1.0\fP and \fI\-\-http2\fP and \fI\-\-http2\-prior\-knowledge\fP and \fI\-\-http3\fP. Added in 7.88.0.
1194 .IP "\-\-http3"
1195-(HTTP) Tells curl to try HTTP/3 to the host in the URL, but fallback to earlier
1196-HTTP versions if the HTTP/3 connection establishment fails. HTTP/3 is only
1197-available for HTTPS and not for HTTP URLs.
1198+(HTTP) Attempt HTTP/3 to the host in the URL, but fallback to earlier HTTP versions
1199+if the HTTP/3 connection establishment fails. HTTP/3 is only available for
1200+HTTPS and not for HTTP URLs.
1201
1202 This option allows a user to avoid using the Alt\-Svc method of upgrading to
1203 HTTP/3 when you know that the target speaks HTTP/3 on the given host and port.
1204@@ -2137,7 +2142,7 @@ Example:
1205 curl --http3 https://example.com
1206 .fi
1207
1208-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.
1209+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\-\-http1.0\fP and \fI\-\-http2\fP and \fI\-\-http2\-prior\-knowledge\fP and \fI\-\-http3\-only\fP. Added in 7.66.0.
1210 .IP "\-\-ignore\-content\-length"
1211 (FTP HTTP) For HTTP, Ignore the Content\-Length header. This is particularly useful for
1212 servers running Apache 1.x, which reports incorrect Content\-Length for
1213@@ -2183,14 +2188,14 @@ and proceed without checking.
1214
1215 When this option is not used for protocols using TLS, curl verifies the
1216 server\(aqs TLS certificate before it continues: that the certificate contains
1217-the right name which matches the host name used in the URL and that the
1218-certificate has been signed by a CA certificate present in the cert store.
1219-See this online resource for further details:
1220+the right name which matches the hostname used in the URL and that the
1221+certificate has been signed by a CA certificate present in the cert store. See
1222+this online resource for further details:
1223 \fBhttps://curl.se/docs/sslcerts.html\fP
1224
1225 For SFTP and SCP, this option makes curl skip the \fIknown_hosts\fP verification.
1226 \fIknown_hosts\fP is a file normally stored in the user\(aqs home directory in the
1227-\&".ssh" subdirectory, which contains host names and their public keys.
1228+\&".ssh" subdirectory, which contains hostnames and their public keys.
1229
1230 \fBWARNING\fP: using this option makes the transfer insecure.
1231
1232@@ -2210,7 +2215,7 @@ Example:
1233 See also \fI\-\-proxy\-insecure\fP, \fI\-\-cacert\fP and \fI\-\-capath\fP.
1234 .IP "\-\-interface <name>"
1235 Perform an operation using a specified interface. You can enter interface
1236-name, IP address or host name. An example could look like:
1237+name, IP address or hostname. An example could look like:
1238 .nf
1239
1240 curl \--interface eth0:1 https://www.example.com/
1241@@ -2229,9 +2234,9 @@ Example:
1242
1243 See also \fI\-\-dns\-interface\fP.
1244 .IP "\-\-ipfs\-gateway <URL>"
1245-(IPFS) Specify which gateway to use for IPFS and IPNS URLs. Not specifying this will
1246-instead make curl check if the IPFS_GATEWAY environment variable is set, or if
1247-a "~/.ipfs/gateway" file holding the gateway URL exists.
1248+(IPFS) Specify which gateway to use for IPFS and IPNS URLs. Not specifying this
1249+instead makes curl check if the IPFS_GATEWAY environment variable is set, or
1250+if a "~/.ipfs/gateway" file holding the gateway URL exists.
1251
1252 If you run a local IPFS node, this gateway is by default available under
1253 \&"http://localhost:8080". A full example URL would look like:
1254@@ -2243,11 +2248,11 @@ curl \--ipfs\-gateway http://localhost:8080 ipfs://bafybeigagd5nmnn2iys2f3doro7y
1255 There are many public IPFS gateways. See for example:
1256 https://ipfs.github.io/public\-gateway\-checker/
1257
1258-WARNING: If you opt to go for a remote gateway you should be aware that you
1259-completely trust the gateway. This is fine in local gateways as you host it
1260-yourself. With remote gateways there could potentially be a malicious actor
1261+If you opt to go for a remote gateway you need to be aware that you completely
1262+trust the gateway. This might be fine in local gateways that you host
1263+yourself. With remote gateways there could potentially be malicious actors
1264 returning you data that does not match the request you made, inspect or even
1265-interfere with the request. You will not notice this when using curl. A
1266+interfere with the request. You may not notice this when using curl. A
1267 mitigation could be to go for a "trustless" gateway. This means you locally
1268 verify that the data. Consult the docs page on trusted vs trustless:
1269 https://docs.ipfs.tech/reference/http/gateway/#trusted\-vs\-trustless
1270@@ -2261,8 +2266,8 @@ Example:
1271
1272 See also \fI-h, \-\-help\fP and \fI-M, \-\-manual\fP. Added in 8.4.0.
1273 .IP "\-4, \-\-ipv4"
1274-This option tells curl to use IPv4 addresses only when resolving host names,
1275-and not for example try IPv6.
1276+Use IPv4 addresses only when resolving hostnames, and not for example try
1277+IPv6.
1278
1279 Providing --ipv4 multiple times has no extra effect.
1280
1281@@ -2273,8 +2278,12 @@ Example:
1282
1283 See also \fI\-\-http1.1\fP and \fI\-\-http2\fP. This option is mutually exclusive to \fI-6, \-\-ipv6\fP.
1284 .IP "\-6, \-\-ipv6"
1285-This option tells curl to use IPv6 addresses only when resolving host names,
1286-and not for example try IPv4.
1287+Use IPv6 addresses only when resolving hostnames, and not for example try
1288+IPv4.
1289+
1290+Your resolver may respond to an IPv6\-only resolve request by returning IPv6
1291+addresses that contain "mapped" IPv4 addresses for compatibility purposes.
1292+macOS is known to do this.
1293
1294 Providing --ipv6 multiple times has no extra effect.
1295
1296@@ -2297,10 +2306,10 @@ works as a shortcut for passing on these three options:
1297 There is \fBno verification\fP that the passed in data is actual JSON or that
1298 the syntax is correct.
1299
1300-If you start the data with the letter @, the rest should be a file name to
1301-read the data from, or a single dash (\-) if you want curl to read the data
1302-from stdin. Posting data from a file named \(aqfoobar\(aq would thus be done with
1303-\fI\-\-json\fP @foobar and to instead read the data from stdin, use \fI\-\-json\fP @\-.
1304+If you start the data with the letter @, the rest should be a filename to read
1305+the data from, or a single dash (\-) if you want curl to read the data from
1306+stdin. Posting data from a file named \(aqfoobar\(aq would thus be done with \fI\-\-json\fP
1307+@foobar and to instead read the data from stdin, use \fI\-\-json\fP @\-.
1308
1309 If this option is used more than once on the same command line, the additional
1310 data pieces are concatenated to the previous before sending.
1311@@ -2333,14 +2342,13 @@ Example:
1312
1313 See also \fI-b, \-\-cookie\fP and \fI-c, \-\-cookie\-jar\fP.
1314 .IP "\-\-keepalive\-time <seconds>"
1315-This option sets the time a connection needs to remain idle before sending
1316-keepalive probes and the time between individual keepalive probes. It is
1317-currently effective on operating systems offering the "TCP_KEEPIDLE" and
1318-\&"TCP_KEEPINTVL" socket options (meaning Linux, recent AIX, HP\-UX and more).
1319-Keepalive is used by the TCP stack to detect broken networks on idle
1320-connections. The number of missed keepalive probes before declaring the
1321-connection down is OS dependent and is commonly 9 or 10. This option has no
1322-effect if \fI\-\-no\-keepalive\fP is used.
1323+Set the time a connection needs to remain idle before sending keepalive probes
1324+and the time between individual keepalive probes. It is currently effective on
1325+operating systems offering the "TCP_KEEPIDLE" and "TCP_KEEPINTVL" socket
1326+options (meaning Linux, recent AIX, HP\-UX and more). Keepalive is used by the
1327+TCP stack to detect broken networks on idle connections. The number of missed
1328+keepalive probes before declaring the connection down is OS dependent and is
1329+commonly 9 or 10. This option has no effect if \fI\-\-no\-keepalive\fP is used.
1330
1331 If unspecified, the option defaults to 60 seconds.
1332
1333@@ -2365,7 +2373,7 @@ Example:
1334
1335 See also \fI\-\-key\fP.
1336 .IP "\-\-key <key>"
1337-(TLS SSH) Private key file name. Allows you to provide your private key in this separate
1338+(TLS SSH) Private key filename. Allows you to provide your private key in this separate
1339 file. For SSH, if not specified, curl tries the following candidates in order:
1340 \&"~/.ssh/id_rsa", "~/.ssh/id_dsa", "./id_rsa", "./id_dsa".
1341
1342@@ -2419,8 +2427,8 @@ Example:
1343 See also \fI-v, \-\-verbose\fP.
1344 .IP "\-\-limit\-rate <speed>"
1345 Specify the maximum transfer rate you want curl to use \- for both downloads
1346-and uploads. This feature is useful if you have a limited pipe and you would like
1347-your transfer not to use your entire bandwidth. To make it slower than it
1348+and uploads. This feature is useful if you have a limited pipe and you would
1349+like your transfer not to use your entire bandwidth. To make it slower than it
1350 otherwise would be.
1351
1352 The given speed is measured in bytes/second, unless a suffix is appended.
1353@@ -2446,23 +2454,20 @@ Examples:
1354
1355 See also \fI\-\-rate\fP, \fI-Y, \-\-speed\-limit\fP and \fI-y, \-\-speed\-time\fP.
1356 .IP "\-l, \-\-list\-only"
1357-(FTP POP3 SFTP) (FTP)
1358-When listing an FTP directory, this switch forces a name\-only view. This is
1359-especially useful if the user wants to machine\-parse the contents of an FTP
1360-directory since the normal directory view does not use a standard look or
1361-format. When used like this, the option causes an NLST command to be sent to
1362-the server instead of LIST.
1363+(FTP POP3 SFTP) When listing an FTP directory, force a name\-only view. Maybe particularly
1364+useful if the user wants to machine\-parse the contents of an FTP directory
1365+since the normal directory view does not use a standard look or format. When
1366+used like this, the option causes an NLST command to be sent to the server
1367+instead of LIST.
1368
1369 Note: Some FTP servers list only files in their response to NLST; they do not
1370 include sub\-directories and symbolic links.
1371
1372-(SFTP)
1373-When listing an SFTP directory, this switch forces a name\-only view, one per line.
1374-This is especially useful if the user wants to machine\-parse the contents of an
1375-SFTP directory since the normal directory view provides more information than just
1376-file names.
1377+When listing an SFTP directory, this switch forces a name\-only view, one per
1378+line. This is especially useful if the user wants to machine\-parse the
1379+contents of an SFTP directory since the normal directory view provides more
1380+information than just filenames.
1381
1382-(POP3)
1383 When retrieving a specific email from POP3, this switch forces a LIST command
1384 to be performed instead of RETR. This is particularly useful if the user wants
1385 to see if a specific message\-id exists on the server and what size it is.
1386@@ -2480,7 +2485,7 @@ Example:
1387 .fi
1388
1389 See also \fI-Q, \-\-quote\fP and \fI-X, \-\-request\fP.
1390-.IP "\-\-local\-port <num/range>"
1391+.IP "\-\-local\-port <range>"
1392 Set a preferred single number or range (FROM\-TO) of local port numbers to use
1393 for the connection(s). Note that port numbers by nature are a scarce resource
1394 so setting this range to something too narrow might cause unnecessary
1395@@ -2497,8 +2502,8 @@ See also \fI-g, \-\-globoff\fP.
1396 .IP "\-\-location\-trusted"
1397 (HTTP) Like \fI\-L, \-\-location\fP, but allows sending the name + password to all hosts that the
1398 site may redirect to. This may or may not introduce a security breach if the
1399-site redirects you to a site to which you send your authentication info
1400-(which is clear\-text in the case of HTTP Basic authentication).
1401+site redirects you to a site to which you send your authentication info (which
1402+is clear\-text in the case of HTTP Basic authentication).
1403
1404 Providing --location-trusted multiple times has no extra effect.
1405 Disable it again with \-\-no-location-trusted.
1406@@ -2611,12 +2616,12 @@ Example:
1407
1408 See also \fI\-\-mail\-rcpt\fP. Added in 7.69.0.
1409 .IP "\-\-mail\-rcpt <address>"
1410-(SMTP) Specify a single email address, user name or mailing list name. Repeat this
1411+(SMTP) Specify a single email address, username or mailing list name. Repeat this
1412 option several times to send to multiple recipients.
1413
1414-When performing an address verification (\fBVRFY\fP command), the recipient should be
1415-specified as the user name or user name and domain (as per Section 3.5 of
1416-RFC 5321).
1417+When performing an address verification (\fBVRFY\fP command), the recipient
1418+should be specified as the username or username and domain (as per Section 3.5
1419+of RFC 5321).
1420
1421 When performing a mailing list expand (EXPN command), the recipient should be
1422 specified using the mailing list name, such as "Friends" or "London\-Office".
1423@@ -2676,10 +2681,10 @@ Example:
1424 .fi
1425
1426 See also \fI-L, \-\-location\fP.
1427-.IP "\-m, \-\-max\-time <fractional seconds>"
1428-Maximum time in seconds that you allow each transfer to take. This is useful
1429-for preventing your batch jobs from hanging for hours due to slow networks or
1430-links going down. This option accepts decimal values.
1431+.IP "\-m, \-\-max\-time <seconds>"
1432+Set maximum time in seconds that you allow each transfer to take. Prevents
1433+your batch jobs from hanging for hours due to slow networks or links going
1434+down. This option accepts decimal values.
1435
1436 If you enable retrying the transfer (\fI\-\-retry\fP) then the maximum time counter is
1437 reset each time the transfer is retried. You can use \fI\-\-retry\-max\-time\fP to limit
1438@@ -2710,13 +2715,13 @@ Example:
1439
1440 See also \fI-Z, \-\-parallel\fP.
1441 .IP "\-\-negotiate"
1442-(HTTP) Enables Negotiate (SPNEGO) authentication.
1443+(HTTP) Enable Negotiate (SPNEGO) authentication.
1444
1445 This option requires a library built with GSS\-API or SSPI support. Use
1446 \fI\-V, \-\-version\fP to see if your curl supports GSS\-API/SSPI or SPNEGO.
1447
1448 When using this option, you must also provide a fake \fI\-u, \-\-user\fP option to activate
1449-the authentication code properly. Sending a \(aq\-u :\(aq is enough as the user name
1450+the authentication code properly. Sending a \(aq\-u :\(aq is enough as the username
1451 and password from the \fI\-u, \-\-user\fP option are not actually used.
1452
1453 Providing --negotiate multiple times has no extra effect.
1454@@ -2728,9 +2733,8 @@ Example:
1455
1456 See also \fI\-\-basic\fP, \fI\-\-ntlm\fP, \fI\-\-anyauth\fP and \fI\-\-proxy\-negotiate\fP.
1457 .IP "\-\-netrc\-file <filename>"
1458-This option is similar to \fI\-n, \-\-netrc\fP, except that you provide the path (absolute
1459-or relative) to the netrc file that curl should use. You can only specify one
1460-netrc file per invocation.
1461+Set the netrc file to use. Similar to \fI\-n, \-\-netrc\fP, except that you also provide
1462+the path (absolute or relative).
1463
1464 It abides by \fI\-\-netrc\-optional\fP if specified.
1465
1466@@ -2756,7 +2760,7 @@ Example:
1467
1468 See also \fI\-\-netrc\-file\fP. This option is mutually exclusive to \fI-n, \-\-netrc\fP.
1469 .IP "\-n, \-\-netrc"
1470-Makes curl scan the \fI.netrc\fP file in the user\(aqs home directory for login name
1471+Make curl scan the \fI.netrc\fP file in the user\(aqs home directory for login name
1472 and password. This is typically used for FTP on Unix. If used with HTTP, curl
1473 enables user authentication. See \fInetrc(5)\fP and \fIftp(1)\fP for details on the
1474 file format. Curl does not complain if that file does not have the right
1475@@ -2768,8 +2772,8 @@ On Windows two filenames in the home directory are checked: \fI.netrc\fP and
1476 only.
1477
1478 A quick and simple example of how to setup a \fI.netrc\fP to allow curl to FTP to
1479-the machine host.domain.com with user name \(aqmyself\(aq and password \(aqsecret\(aq
1480-could look similar to:
1481+the machine host.domain.com with username \(aqmyself\(aq and password \(aqsecret\(aq could
1482+look similar to:
1483 .nf
1484
1485 machine host.domain.com
1486@@ -2786,10 +2790,9 @@ Example:
1487
1488 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.
1489 .IP "\-:, \-\-next"
1490-Tells curl to use a separate operation for the following URL and associated
1491-options. This allows you to send several URL requests, each with their own
1492-specific options, for example, such as different user names or custom requests
1493-for each.
1494+Use a separate operation for the following URL and associated options. This
1495+allows you to send several URL requests, each with their own specific options,
1496+for example, such as different usernames or custom requests for each.
1497
1498 \fI\-:, \-\-next\fP resets all local options and only global ones have their values survive
1499 over to the operation following the \fI\-:, \-\-next\fP instruction. Global options include
1500@@ -2814,7 +2817,7 @@ See also \fI-Z, \-\-parallel\fP and \fI-K, \-\-config\fP.
1501 with an SSL library that supports ALPN. ALPN is used by a libcurl that supports
1502 HTTP/2 to negotiate HTTP/2 support with the server during https sessions.
1503
1504-Note that this is the negated option name documented. You can use \--alpn to
1505+Note that this is the negated option name documented. You can use \fI\-\-alpn\fP to
1506 enable ALPN.
1507
1508 Providing --no-alpn multiple times has no extra effect.
1509@@ -2832,7 +2835,7 @@ uses a standard buffered output stream that has the effect that it outputs the
1510 data in chunks, not necessarily exactly when the data arrives. Using this
1511 option disables that buffering.
1512
1513-Note that this is the negated option name documented. You can use \--buffer to
1514+Note that this is the negated option name documented. You can use \fI\-\-buffer\fP to
1515 enable buffering again.
1516
1517 Providing --no-buffer multiple times has no extra effect.
1518@@ -2852,7 +2855,7 @@ the file that would be created, up to filename.100 after which it does not
1519 create any file.
1520
1521 Note that this is the negated option name documented. You can thus use
1522--\-clobber to enforce the clobbering, even if \fI\-J, \-\-remote\-header\-name\fP is
1523+\fI\-\-clobber\fP to enforce the clobbering, even if \fI\-J, \-\-remote\-header\-name\fP is
1524 specified.
1525
1526 Providing --no-clobber multiple times has no extra effect.
1527@@ -2869,7 +2872,7 @@ Disables the use of keepalive messages on the TCP connection. curl otherwise
1528 enables them by default.
1529
1530 Note that this is the negated option name documented. You can thus use
1531--\-keepalive to enforce keepalive.
1532+\fI\-\-keepalive\fP to enforce keepalive.
1533
1534 Providing --no-keepalive multiple times has no extra effect.
1535 Disable it again with \-\-keepalive.
1536@@ -2901,7 +2904,7 @@ Option to switch off the progress meter output without muting or otherwise
1537 affecting warning and informational messages like \fI\-s, \-\-silent\fP does.
1538
1539 Note that this is the negated option name documented. You can thus use
1540--\-progress\-meter to enable the progress meter again.
1541+\fI\-\-progress\-meter\fP to enable the progress meter again.
1542
1543 Providing --no-progress-meter multiple times has no extra effect.
1544 Disable it again with \-\-progress-meter.
1545@@ -2920,7 +2923,7 @@ implementations in the wild that may require you to disable this in order for
1546 you to succeed.
1547
1548 Note that this is the negated option name documented. You can thus use
1549--\-sessionid to enforce session\-ID caching.
1550+\fI\-\-sessionid\fP to enforce session\-ID caching.
1551
1552 Providing --no-sessionid multiple times has no extra effect.
1553 Disable it again with \-\-sessionid.
1554@@ -2970,7 +2973,7 @@ Example:
1555
1556 See also \fI\-\-ntlm\fP and \fI\-\-proxy\-ntlm\fP.
1557 .IP "\-\-ntlm"
1558-(HTTP) Enables NTLM authentication. The NTLM authentication method was designed by
1559+(HTTP) Use NTLM authentication. The NTLM authentication method was designed by
1560 Microsoft and is used by IIS web servers. It is a proprietary protocol,
1561 reverse\-engineered by clever people and implemented in curl based on their
1562 efforts. This kind of behavior should not be endorsed, you should encourage
1563@@ -2990,10 +2993,10 @@ Example:
1564 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.
1565 .IP "\-\-oauth2\-bearer <token>"
1566 (IMAP LDAP POP3 SMTP HTTP) Specify the Bearer Token for OAUTH 2.0 server authentication. The Bearer Token
1567-is used in conjunction with the user name which can be specified as part of
1568-the \fI\-\-url\fP or \fI\-u, \-\-user\fP options.
1569+is used in conjunction with the username which can be specified as part of the
1570+\fI\-\-url\fP or \fI\-u, \-\-user\fP options.
1571
1572-The Bearer Token and user name are formatted according to RFC 6750.
1573+The Bearer Token and username are formatted according to RFC 6750.
1574
1575 If --oauth2-bearer is provided several times, the last set value is used.
1576
1577@@ -3004,8 +3007,8 @@ Example:
1578
1579 See also \fI\-\-basic\fP, \fI\-\-ntlm\fP and \fI\-\-digest\fP.
1580 .IP "\-\-output\-dir <dir>"
1581-This option specifies the directory in which files should be stored, when
1582-\fI\-O, \-\-remote\-name\fP or \fI\-o, \-\-output\fP are used.
1583+Specify the directory in which files should be stored, when \fI\-O, \-\-remote\-name\fP or
1584+\fI\-o, \-\-output\fP are used.
1585
1586 The given output directory is used for all URLs and output options on the
1587 command line, up until the first \fI\-:, \-\-next\fP.
1588@@ -3022,10 +3025,10 @@ Example:
1589
1590 See also \fI-O, \-\-remote\-name\fP and \fI-J, \-\-remote\-header\-name\fP. Added in 7.73.0.
1591 .IP "\-o, \-\-output <file>"
1592-Write output to <file> instead of stdout. If you are using {} or [] to fetch
1593-multiple documents, you should quote the URL and you can use \(aq#\(aq followed by a
1594-number in the <file> specifier. That variable is replaced with the current
1595-string for the URL being fetched. Like in:
1596+Write output to the given file instead of stdout. If you are using globbing to
1597+fetch multiple documents, you should quote the URL and you can use "#"
1598+followed by a number in the filename. That variable is then replaced with the
1599+current string for the URL being fetched. Like in:
1600 .nf
1601
1602 curl "http://{one,two}.example.com" \-o "file_#1.txt"
1603@@ -3067,6 +3070,13 @@ Or for Windows:
1604 .nf
1605
1606 curl example.com \-o nul
1607+.fi
1608+
1609+Specify the filename as single minus to force the output to stdout, to
1610+override curl\(aqs internal binary output in terminal prevention:
1611+.nf
1612+
1613+curl https://example.com/jpeg \-o \-
1614
1615 --output can be used several times in a command line
1616
1617@@ -3140,9 +3150,9 @@ Example:
1618
1619 See also \fI\-\-key\fP and \fI-u, \-\-user\fP.
1620 .IP "\-\-path\-as\-is"
1621-Tell curl to not handle sequences of /../ or /./ in the given URL
1622-path. Normally curl squashes or merges them according to standards but with
1623-this option set you tell it not to do that.
1624+Do not handle sequences of /../ or /./ in the given URL path. Normally curl
1625+squashes or merges them according to standards but with this option set you
1626+tell it not to do that.
1627
1628 Providing --path-as-is multiple times has no extra effect.
1629 Disable it again with \-\-no-path-as-is.
1630@@ -3154,10 +3164,10 @@ Example:
1631
1632 See also \fI\-\-request\-target\fP.
1633 .IP "\-\-pinnedpubkey <hashes>"
1634-(TLS) Tells curl to use the specified public key file (or hashes) to verify the
1635-peer. This can be a path to a file which contains a single public key in PEM
1636-or DER format, or any number of base64 encoded sha256 hashes preceded by
1637-\(aqsha256//\(aq and separated by \(aq;\(aq.
1638+(TLS) Use the specified public key file (or hashes) to verify the peer. This can be
1639+a path to a file which contains a single public key in PEM or DER format, or
1640+any number of base64 encoded sha256 hashes preceded by \(aqsha256//\(aq and
1641+separated by \(aq;\(aq.
1642
1643 When negotiating a TLS or SSL connection, the server sends a certificate
1644 indicating its identity. A public key is extracted from this certificate and
1645@@ -3190,11 +3200,11 @@ Examples:
1646
1647 See also \fI\-\-hostpubsha256\fP.
1648 .IP "\-\-post301"
1649-(HTTP) Tells curl to respect RFC 7231/6.4.2 and not convert POST requests into GET
1650-requests when following a 301 redirection. The non\-RFC behavior is ubiquitous
1651-in web browsers, so curl does the conversion by default to maintain
1652-consistency. However, a server may require a POST to remain a POST after such
1653-a redirection. This option is meaningful only when using \fI\-L, \-\-location\fP.
1654+(HTTP) Respect RFC 7231/6.4.2 and do not convert POST requests into GET requests when
1655+following a 301 redirect. The non\-RFC behavior is ubiquitous in web browsers,
1656+so curl does the conversion by default to maintain consistency. However, a
1657+server may require a POST to remain a POST after such a redirection. This
1658+option is meaningful only when using \fI\-L, \-\-location\fP.
1659
1660 Providing --post301 multiple times has no extra effect.
1661 Disable it again with \-\-no-post301.
1662@@ -3206,11 +3216,11 @@ Example:
1663
1664 See also \fI\-\-post302\fP, \fI\-\-post303\fP and \fI-L, \-\-location\fP.
1665 .IP "\-\-post302"
1666-(HTTP) Tells curl to respect RFC 7231/6.4.3 and not convert POST requests into GET
1667-requests when following a 302 redirection. The non\-RFC behavior is ubiquitous
1668-in web browsers, so curl does the conversion by default to maintain
1669-consistency. However, a server may require a POST to remain a POST after such
1670-a redirection. This option is meaningful only when using \fI\-L, \-\-location\fP.
1671+(HTTP) Respect RFC 7231/6.4.3 and do not convert POST requests into GET requests when
1672+following a 302 redirect. The non\-RFC behavior is ubiquitous in web browsers,
1673+so curl does the conversion by default to maintain consistency. However, a
1674+server may require a POST to remain a POST after such a redirection. This
1675+option is meaningful only when using \fI\-L, \-\-location\fP.
1676
1677 Providing --post302 multiple times has no extra effect.
1678 Disable it again with \-\-no-post302.
1679@@ -3222,10 +3232,9 @@ Example:
1680
1681 See also \fI\-\-post301\fP, \fI\-\-post303\fP and \fI-L, \-\-location\fP.
1682 .IP "\-\-post303"
1683-(HTTP) Tells curl to violate RFC 7231/6.4.4 and not convert POST requests into GET
1684-requests when following 303 redirections. A server may require a POST to
1685-remain a POST after a 303 redirection. This option is meaningful only when
1686-using \fI\-L, \-\-location\fP.
1687+(HTTP) Violate RFC 7231/6.4.4 and do not convert POST requests into GET requests when
1688+following 303 redirect. A server may require a POST to remain a POST after a
1689+303 redirection. This option is meaningful only when using \fI\-L, \-\-location\fP.
1690
1691 Providing --post303 multiple times has no extra effect.
1692 Disable it again with \-\-no-post303.
1693@@ -3283,14 +3292,13 @@ Example:
1694
1695 See also \fI\-\-styled\-output\fP.
1696 .IP "\-\-proto\-default <protocol>"
1697-Tells curl to use \fIprotocol\fP for any URL missing a scheme name.
1698+Use \fIprotocol\fP for any provided URL missing a scheme.
1699
1700-An unknown or unsupported protocol causes error
1701-\fICURLE_UNSUPPORTED_PROTOCOL\fP (1).
1702+An unknown or unsupported protocol causes error \fICURLE_UNSUPPORTED_PROTOCOL\fP.
1703
1704 This option does not change the default proxy protocol (http).
1705
1706-Without this option set, curl guesses protocol based on the host name, see
1707+Without this option set, curl guesses protocol based on the hostname, see
1708 \fI\-\-url\fP for details.
1709
1710 If --proto-default is provided several times, the last set value is used.
1711@@ -3302,9 +3310,8 @@ Example:
1712
1713 See also \fI\-\-proto\fP and \fI\-\-proto\-redir\fP.
1714 .IP "\-\-proto\-redir <protocols>"
1715-Tells curl to limit what protocols it may use on redirect. Protocols denied by
1716-\fI\-\-proto\fP are not overridden by this option. See \fI\-\-proto\fP for how protocols are
1717-represented.
1718+Limit what protocols to allow on redirects. Protocols denied by \fI\-\-proto\fP are
1719+not overridden by this option. See \fI\-\-proto\fP for how protocols are represented.
1720
1721 Example, allow only HTTP and HTTPS on redirect:
1722 .nf
1723@@ -3325,9 +3332,9 @@ Example:
1724
1725 See also \fI\-\-proto\fP.
1726 .IP "\-\-proto <protocols>"
1727-Tells curl to limit what protocols it may use for transfers. Protocols are
1728-evaluated left to right, are comma separated, and are each a protocol name or
1729-\(aqall\(aq, optionally prefixed by zero or more modifiers. Available modifiers are:
1730+Limit what protocols to allow for transfers. Protocols are evaluated left to
1731+right, are comma separated, and are each a protocol name or \(aqall\(aq, optionally
1732+prefixed by zero or more modifiers. Available modifiers are:
1733 .RS
1734 .IP +
1735 Permit this protocol in addition to protocols already permitted (this is
1736@@ -3352,8 +3359,6 @@ relying upon support for that protocol being built into curl to avoid an error.
1737
1738 This option can be used multiple times, in which case the effect is the same
1739 as concatenating the protocols into one instance of the option.
1740-.RE
1741-.IP
1742
1743 If --proto is provided several times, the last set value is used.
1744
1745@@ -3364,7 +3369,7 @@ Example:
1746
1747 See also \fI\-\-proto\-redir\fP and \fI\-\-proto\-default\fP.
1748 .IP "\-\-proxy\-anyauth"
1749-Tells curl to pick a suitable authentication method when communicating with
1750+Automatically pick a suitable authentication method when communicating with
1751 the given HTTP proxy. This might cause an extra request/response round\-trip.
1752
1753 Providing --proxy-anyauth multiple times has no extra effect.
1754@@ -3376,9 +3381,9 @@ Example:
1755
1756 See also \fI-x, \-\-proxy\fP, \fI\-\-proxy\-basic\fP and \fI\-\-proxy\-digest\fP.
1757 .IP "\-\-proxy\-basic"
1758-Tells curl to use HTTP Basic authentication when communicating with the given
1759-proxy. Use \fI\-\-basic\fP for enabling HTTP Basic with a remote host. Basic is the
1760-default authentication method curl uses with proxies.
1761+Use HTTP Basic authentication when communicating with the given proxy. Use
1762+\fI\-\-basic\fP for enabling HTTP Basic with a remote host. Basic is the default
1763+authentication method curl uses with proxies.
1764
1765 Providing --proxy-basic multiple times has no extra effect.
1766
1767@@ -3389,10 +3394,9 @@ Example:
1768
1769 See also \fI-x, \-\-proxy\fP, \fI\-\-proxy\-anyauth\fP and \fI\-\-proxy\-digest\fP.
1770 .IP "\-\-proxy\-ca\-native"
1771-(TLS) Tells curl to use the CA store from the native operating system to verify the
1772-HTTPS proxy. By default, curl uses a CA store provided in a single file or
1773-directory, but when using this option it interfaces the operating system\(aqs own
1774-vault.
1775+(TLS) Use the CA store from the native operating system to verify the HTTPS proxy.
1776+By default, curl uses a CA store provided in a single file or directory, but
1777+when using this option it interfaces the operating system\(aqs own vault.
1778
1779 This option works for curl on Windows when built to use OpenSSL, wolfSSL
1780 (added in 8.3.0) or GnuTLS (added in 8.5.0). When curl on Windows is built to
1781@@ -3422,6 +3426,16 @@ See also \fI\-\-proxy\-capath\fP, \fI\-\-cacert\fP, \fI\-\-capath\fP and \fI-x,
1782 .IP "\-\-proxy\-capath <dir>"
1783 Same as \fI\-\-capath\fP but used in HTTPS proxy context.
1784
1785+Use the specified certificate directory to verify the proxy. Multiple paths
1786+can be provided by separated with colon (":") (e.g. "path1:path2:path3"). The
1787+certificates must be in PEM format, and if curl is built against OpenSSL, the
1788+directory must have been processed using the c_rehash utility supplied with
1789+OpenSSL. Using \fI\-\-proxy\-capath\fP can allow OpenSSL\-powered curl to make
1790+SSL\-connections much more efficiently than using \fI\-\-proxy\-cacert\fP if the
1791+\fI\-\-proxy\-cacert\fP file contains many CA certificates.
1792+
1793+If this option is set, the default capath value is ignored.
1794+
1795 If --proxy-capath is provided several times, the last set value is used.
1796
1797 Example:
1798@@ -3481,8 +3495,8 @@ Example:
1799
1800 See also \fI\-\-crlfile\fP and \fI-x, \-\-proxy\fP. Added in 7.52.0.
1801 .IP "\-\-proxy\-digest"
1802-Tells curl to use HTTP Digest authentication when communicating with the given
1803-proxy. Use \fI\-\-digest\fP for enabling HTTP Digest with a remote host.
1804+Use HTTP Digest authentication when communicating with the given proxy. Use
1805+\fI\-\-digest\fP for enabling HTTP Digest with a remote host.
1806
1807 Providing --proxy-digest multiple times has no extra effect.
1808
1809@@ -3523,8 +3537,8 @@ Examples:
1810
1811 See also \fI-x, \-\-proxy\fP.
1812 .IP "\-\-proxy\-http2"
1813-(HTTP) Tells curl to try negotiate HTTP version 2 with an HTTPS proxy. The proxy might
1814-still only offer HTTP/1 and then curl sticks to using that version.
1815+(HTTP) Negotiate HTTP/2 with an HTTPS proxy. The proxy might still only offer HTTP/1
1816+and then curl sticks to using that version.
1817
1818 This has no effect for any other kinds of proxies.
1819
1820@@ -3540,6 +3554,18 @@ See also \fI-x, \-\-proxy\fP. \fI\-\-proxy\-http2\fP requires that the underlyin
1821 .IP "\-\-proxy\-insecure"
1822 Same as \fI\-k, \-\-insecure\fP but used in HTTPS proxy context.
1823
1824+Every secure connection curl makes is verified to be secure before the
1825+transfer takes place. This option makes curl skip the verification step with a
1826+proxy and proceed without checking.
1827+
1828+When this option is not used for a proxy using HTTPS, curl verifies the
1829+proxy\(aqs TLS certificate before it continues: that the certificate contains the
1830+right name which matches the hostname and that the certificate has been signed
1831+by a CA certificate present in the cert store. See this online resource for
1832+further details: \fBhttps://curl.se/docs/sslcerts.html\fP
1833+
1834+\fBWARNING\fP: using this option makes the transfer to the proxy insecure.
1835+
1836 Providing --proxy-insecure multiple times has no extra effect.
1837 Disable it again with \-\-no-proxy-insecure.
1838
1839@@ -3572,9 +3598,9 @@ Example:
1840
1841 See also \fI\-\-proxy\-key\-type\fP and \fI-x, \-\-proxy\fP. Added in 7.52.0.
1842 .IP "\-\-proxy\-negotiate"
1843-Tells curl to use HTTP Negotiate (SPNEGO) authentication when communicating
1844-with the given proxy. Use \fI\-\-negotiate\fP for enabling HTTP Negotiate (SPNEGO)
1845-with a remote host.
1846+Use HTTP Negotiate (SPNEGO) authentication when communicating with the given
1847+proxy. Use \fI\-\-negotiate\fP for enabling HTTP Negotiate (SPNEGO) with a remote
1848+host.
1849
1850 Providing --proxy-negotiate multiple times has no extra effect.
1851
1852@@ -3585,8 +3611,8 @@ Example:
1853
1854 See also \fI\-\-proxy\-anyauth\fP and \fI\-\-proxy\-basic\fP.
1855 .IP "\-\-proxy\-ntlm"
1856-Tells curl to use HTTP NTLM authentication when communicating with the given
1857-proxy. Use \fI\-\-ntlm\fP for enabling NTLM with a remote host.
1858+Use HTTP NTLM authentication when communicating with the given proxy. Use
1859+\fI\-\-ntlm\fP for enabling NTLM with a remote host.
1860
1861 Providing --proxy-ntlm multiple times has no extra effect.
1862
1863@@ -3608,10 +3634,10 @@ Example:
1864
1865 See also \fI-x, \-\-proxy\fP and \fI\-\-proxy\-key\fP. Added in 7.52.0.
1866 .IP "\-\-proxy\-pinnedpubkey <hashes>"
1867-(TLS) Tells curl to use the specified public key file (or hashes) to verify the
1868-proxy. This can be a path to a file which contains a single public key in PEM
1869-or DER format, or any number of base64 encoded sha256 hashes preceded by
1870-\(aqsha256//\(aq and separated by \(aq;\(aq.
1871+(TLS) Use the specified public key file (or hashes) to verify the proxy. This can be
1872+a path to a file which contains a single public key in PEM or DER format, or
1873+any number of base64 encoded sha256 hashes preceded by \(aqsha256//\(aq and
1874+separated by \(aq;\(aq.
1875
1876 When negotiating a TLS or SSL connection, the server sends a certificate
1877 indicating its identity. A public key is extracted from this certificate and
1878@@ -3628,7 +3654,7 @@ Examples:
1879
1880 See also \fI\-\-pinnedpubkey\fP and \fI-x, \-\-proxy\fP. Added in 7.59.0.
1881 .IP "\-\-proxy\-service\-name <name>"
1882-This option allows you to change the service name for proxy negotiation.
1883+Set the service name for proxy negotiation.
1884
1885 If --proxy-service-name is provided several times, the last set value is used.
1886
1887@@ -3653,6 +3679,8 @@ See also \fI\-\-ssl\-allow\-beast\fP and \fI-x, \-\-proxy\fP. Added in 7.52.0.
1888 .IP "\-\-proxy\-ssl\-auto\-client\-cert"
1889 Same as \fI\-\-ssl\-auto\-client\-cert\fP but used in HTTPS proxy context.
1890
1891+This is only supported by Schannel.
1892+
1893 Providing --proxy-ssl-auto-client-cert multiple times has no extra effect.
1894 Disable it again with \-\-no-proxy-ssl-auto-client-cert.
1895
1896@@ -3663,9 +3691,9 @@ Example:
1897
1898 See also \fI\-\-ssl\-auto\-client\-cert\fP and \fI-x, \-\-proxy\fP. Added in 7.77.0.
1899 .IP "\-\-proxy\-tls13\-ciphers <ciphersuite list>"
1900-(TLS) Specifies which cipher suites to use in the connection to your HTTPS proxy
1901-when it negotiates TLS 1.3. The list of ciphers suites must specify valid
1902-ciphers. Read up on TLS 1.3 cipher suite details on this URL:
1903+(TLS) Specify which cipher suites to use in the connection to your HTTPS proxy when
1904+it negotiates TLS 1.3. The list of ciphers suites must specify valid ciphers.
1905+Read up on TLS 1.3 cipher suite details on this URL:
1906
1907 https://curl.se/docs/ssl\-ciphers.html
1908
1909@@ -3726,11 +3754,11 @@ Example:
1910
1911 See also \fI-x, \-\-proxy\fP. Added in 7.52.0.
1912 .IP "\-U, \-\-proxy\-user <user:password>"
1913-Specify the user name and password to use for proxy authentication.
1914+Specify the username and password to use for proxy authentication.
1915
1916 If you use a Windows SSPI\-enabled curl binary and do either Negotiate or NTLM
1917-authentication then you can tell curl to select the user name and password
1918-from your environment by specifying a single colon with this option: "\-U :".
1919+authentication then you can tell curl to select the username and password from
1920+your environment by specifying a single colon with this option: "\-U :".
1921
1922 On systems where it works, curl hides the given option argument from process
1923 listings. This is not enough to protect credentials from possibly getting seen
1924@@ -3742,7 +3770,7 @@ If --proxy-user is provided several times, the last set value is used.
1925
1926 Example:
1927 .nf
1928- curl --proxy-user name:pwd -x proxy https://example.com
1929+ curl --proxy-user smith:secret -x proxy https://example.com
1930 .fi
1931
1932 See also \fI\-\-proxy\-pass\fP.
1933@@ -3807,7 +3835,7 @@ Providing --proxy1.0 multiple times has no extra effect.
1934
1935 Example:
1936 .nf
1937- curl --proxy1.0 -x http://proxy https://example.com
1938+ curl --proxy1.0 http://proxy https://example.com
1939 .fi
1940
1941 See also \fI-x, \-\-proxy\fP, \fI\-\-socks5\fP and \fI\-\-preproxy\fP.
1942@@ -3830,7 +3858,7 @@ Example:
1943
1944 See also \fI-x, \-\-proxy\fP.
1945 .IP "\-\-pubkey <key>"
1946-(SFTP SCP) Public key file name. Allows you to provide your public key in this separate
1947+(SFTP SCP) Public key filename. Allows you to provide your public key in this separate
1948 file.
1949
1950 curl attempts to automatically extract the public key from the private key
1951@@ -3867,13 +3895,13 @@ You must send syntactically correct FTP commands as RFC 959 defines to FTP
1952 servers, or one of the commands listed below to SFTP servers.
1953
1954 SFTP is a binary protocol. Unlike for FTP, curl interprets SFTP quote commands
1955-itself before sending them to the server. File names may be quoted
1956-shell\-style to embed spaces or special characters. Following is the list of
1957-all supported SFTP quote commands:
1958+itself before sending them to the server. Filenames may be quoted shell\-style
1959+to embed spaces or special characters. Following is the list of all supported
1960+SFTP quote commands:
1961 .RS
1962 .IP "atime date file"
1963 The atime command sets the last access time of the file named by the file
1964-operand. The <date expression> can be all sorts of date strings, see the
1965+operand. The date expression can be all sorts of date strings, see the
1966 \fIcurl_getdate(3)\fP man page for date expression details. (Added in 7.73.0)
1967 .IP "chgrp group file"
1968 The chgrp command sets the group ID of the file named by the file operand to
1969@@ -3893,7 +3921,7 @@ pointing to the source_file location.
1970 The mkdir command creates the directory named by the directory_name operand.
1971 .IP "mtime date file"
1972 The mtime command sets the last modification time of the file named by the
1973-file operand. The <date expression> can be all sorts of date strings, see the
1974+file operand. The date expression can be all sorts of date strings, see the
1975 \fIcurl_getdate(3)\fP man page for date expression details. (Added in 7.73.0)
1976 .IP pwd
1977 The pwd command returns the absolute path name of the current working directory.
1978@@ -3965,8 +3993,6 @@ attempt to get a range, curl instead gets the whole document.
1979 FTP and SFTP range downloads only support the simple \(aqstart\-stop\(aq syntax
1980 (optionally with one of the numbers omitted). FTP use depends on the extended
1981 FTP command SIZE.
1982-.RE
1983-.IP
1984
1985 If --range is provided several times, the last set value is used.
1986
1987@@ -4025,11 +4051,11 @@ Example:
1988
1989 See also \fI\-\-tr\-encoding\fP.
1990 .IP "\-e, \-\-referer <URL>"
1991-(HTTP) Sends the "Referrer Page" information to the HTTP server. This can also be set
1992-with the \fI\-H, \-\-header\fP flag of course. When used with \fI\-L, \-\-location\fP you can append
1993-\&";auto" to the \fI\-e, \-\-referer\fP URL to make curl automatically set the previous URL
1994-when it follows a Location: header. The ";auto" string can be used alone,
1995-even if you do not set an initial \fI\-e, \-\-referer\fP.
1996+(HTTP) Set the referrer URL in the HTTP request. This can also be set with the
1997+\fI\-H, \-\-header\fP flag of course. When used with \fI\-L, \-\-location\fP you can append ";auto"" to
1998+the \fI\-e, \-\-referer\fP URL to make curl automatically set the previous URL when it
1999+follows a Location: header. The ";auto" string can be used alone, even if you
2000+do not set an initial \fI\-e, \-\-referer\fP.
2001
2002 If --referer is provided several times, the last set value is used.
2003
2004@@ -4042,21 +4068,20 @@ Examples:
2005
2006 See also \fI-A, \-\-user\-agent\fP and \fI-H, \-\-header\fP.
2007 .IP "\-J, \-\-remote\-header\-name"
2008-(HTTP) This option tells the \fI\-O, \-\-remote\-name\fP option to use the server\-specified
2009-Content\-Disposition filename instead of extracting a filename from the URL. If
2010-the server\-provided file name contains a path, that is stripped off before the
2011-file name is used.
2012+(HTTP) Tell the \fI\-O, \-\-remote\-name\fP option to use the server\-specified Content\-Disposition
2013+filename instead of extracting a filename from the URL. If the server\-provided
2014+filename contains a path, that is stripped off before the filename is used.
2015
2016 The file is saved in the current directory, or in the directory specified with
2017 \fI\-\-output\-dir\fP.
2018
2019-If the server specifies a file name and a file with that name already exists
2020-in the destination directory, it is not overwritten and an error occurs \-
2021-unless you allow it by using the \--clobber option. If the server does not
2022-specify a file name then this option has no effect.
2023+If the server specifies a filename and a file with that name already exists in
2024+the destination directory, it is not overwritten and an error occurs \- unless
2025+you allow it by using the \fI\-\-clobber\fP option. If the server does not specify a
2026+filename then this option has no effect.
2027
2028-There is no attempt to decode %\-sequences (yet) in the provided file name, so
2029-this option may provide you with rather unexpected file names.
2030+There is no attempt to decode %\-sequences (yet) in the provided filename, so
2031+this option may provide you with rather unexpected filenames.
2032
2033 This feature uses the name from the "filename" field, it does not yet support
2034 the "filename*" field (filenames with explicit character sets).
2035@@ -4075,10 +4100,10 @@ Example:
2036
2037 See also \fI-O, \-\-remote\-name\fP.
2038 .IP "\-\-remote\-name\-all"
2039-This option changes the default action for all given URLs to be dealt with as
2040-if \fI\-O, \-\-remote\-name\fP were used for each one. So if you want to disable that for a
2041+Change the default action for all given URLs to be dealt with as if
2042+\fI\-O, \-\-remote\-name\fP were used for each one. If you want to disable that for a
2043 specific URL after \fI\-\-remote\-name\-all\fP has been used, you must use "\-o \-" or
2044--\-no\-remote\-name.
2045+\fI\-\-no\-remote\-name\fP.
2046
2047 Providing --remote-name-all multiple times has no extra effect.
2048 Disable it again with \-\-no-remote-name-all.
2049@@ -4097,14 +4122,14 @@ The file is saved in the current working directory. If you want the file saved
2050 in a different directory, make sure you change the current working directory
2051 before invoking curl with this option or use \fI\-\-output\-dir\fP.
2052
2053-The remote file name to use for saving is extracted from the given URL,
2054-nothing else, and if it already exists it is overwritten. If you want the
2055-server to be able to choose the file name refer to \fI\-J, \-\-remote\-header\-name\fP which
2056-can be used in addition to this option. If the server chooses a file name and
2057-that name already exists it is not overwritten.
2058+The remote filename to use for saving is extracted from the given URL, nothing
2059+else, and if it already exists it is overwritten. If you want the server to be
2060+able to choose the filename refer to \fI\-J, \-\-remote\-header\-name\fP which can be used in
2061+addition to this option. If the server chooses a filename and that name
2062+already exists it is not overwritten.
2063
2064-There is no URL decoding done on the file name. If it has %20 or other URL
2065-encoded parts of the name, they end up as\-is as file name.
2066+There is no URL decoding done on the filename. If it has %20 or other URL
2067+encoded parts of the name, they end up as\-is as filename.
2068
2069 You may use this option as many times as the number of URLs you have.
2070
2071@@ -4131,9 +4156,9 @@ Example:
2072
2073 See also \fI-O, \-\-remote\-name\fP and \fI-z, \-\-time\-cond\fP.
2074 .IP "\-\-remove\-on\-error"
2075-When curl returns an error when told to save output in a local file, this
2076-option removes that saved file before exiting. This prevents curl from
2077-leaving a partial file in the case of an error during transfer.
2078+Remove output file if an error occurs. If curl returns an error when told to
2079+save output in a local file. This prevents curl from leaving a partial file in
2080+the case of an error during transfer.
2081
2082 If the output is not a regular file, this option has no effect.
2083
2084@@ -4147,10 +4172,10 @@ Example:
2085
2086 See also \fI-f, \-\-fail\fP. Added in 7.83.0.
2087 .IP "\-\-request\-target <path>"
2088-(HTTP) Tells curl to use an alternative "target" (path) instead of using the path as
2089-provided in the URL. Particularly useful when wanting to issue HTTP requests
2090-without leading slash or other data that does not follow the regular URL
2091-pattern, like "OPTIONS *".
2092+(HTTP) Use an alternative target (path) instead of using the path as provided in the
2093+URL. Particularly useful when wanting to issue HTTP requests without leading
2094+slash or other data that does not follow the regular URL pattern, like
2095+\&"OPTIONS *".
2096
2097 curl passes on the verbatim string you give it its the request without any
2098 filter or other safe guards. That includes white space and control characters.
2099@@ -4181,7 +4206,7 @@ Normally you do not need this option. All sorts of \fIGET\fP, \fIHEAD\fP, \fIPOS
2100 \fIPUT\fP requests are rather invoked by using dedicated command line options.
2101
2102 This option only changes the actual word used in the HTTP request, it does not
2103-alter the way curl behaves. So for example if you want to make a proper HEAD
2104+alter the way curl behaves. For example if you want to make a proper HEAD
2105 request, using \-X HEAD does not suffice. You need to use the \fI\-I, \-\-head\fP option.
2106
2107 The method string you set with \fI\-X, \-\-request\fP is used for all requests, which
2108@@ -4219,7 +4244,7 @@ the number used for the specific protocol the host is used for. It means
2109 you need several entries if you want to provide address for the same host but
2110 different ports.
2111
2112-By specifying \(aq*\(aq as host you can tell curl to resolve any host and specific
2113+By specifying "*" as host you can tell curl to resolve any host and specific
2114 port pair to the specified address. Wildcard is resolved last so any \fI\-\-resolve\fP
2115 with a specific host and port is used first.
2116
2117@@ -4238,7 +4263,7 @@ Support for providing multiple IP addresses per entry was added in 7.59.0.
2118
2119 Support for resolving with wildcard was added in 7.64.0.
2120
2121-Support for the \(aq+\(aq prefix was was added in 7.75.0.
2122+Support for the \(aq+\(aq prefix was added in 7.75.0.
2123
2124 --resolve can be used several times in a command line
2125
2126@@ -4254,7 +4279,7 @@ Retry on any error. This option is used together with \fI\-\-retry\fP.
2127 This option is the "sledgehammer" of retrying. Do not use this option by
2128 default (for example in your \fBcurlrc\fP), there may be unintended consequences
2129 such as sending or receiving duplicate data. Do not use with redirected input
2130-or output. You\(aqd be much better off handling your unique problems in shell
2131+or output. You might be better off handling your unique problems in a shell
2132 script. Please read the example below.
2133
2134 \fBWARNING\fP: For server compatibility curl attempts to retry failed flaky
2135@@ -4381,7 +4406,7 @@ Example:
2136
2137 See also \fI\-\-sasl\-authzid\fP.
2138 .IP "\-\-service\-name <name>"
2139-This option allows you to change the service name for SPNEGO.
2140+Set the service name for SPNEGO.
2141
2142 If --service-name is provided several times, the last set value is used.
2143
2144@@ -4424,7 +4449,7 @@ Example:
2145 See also \fI-v, \-\-verbose\fP, \fI\-\-stderr\fP and \fI\-\-no\-progress\-meter\fP.
2146 .IP "\-\-socks4 <host[:port]>"
2147 Use the specified SOCKS4 proxy. If the port number is not specified, it is
2148-assumed at port 1080. Using this socket type make curl resolve the host name
2149+assumed at port 1080. Using this socket type make curl resolve the hostname
2150 and passing the address on to the proxy.
2151
2152 To specify proxy on a unix domain socket, use localhost for host, e.g.
2153@@ -4451,7 +4476,7 @@ Example:
2154 See also \fI\-\-socks4a\fP, \fI\-\-socks5\fP and \fI\-\-socks5\-hostname\fP.
2155 .IP "\-\-socks4a <host[:port]>"
2156 Use the specified SOCKS4a proxy. If the port number is not specified, it is
2157-assumed at port 1080. This asks the proxy to resolve the host name.
2158+assumed at port 1080. This asks the proxy to resolve the hostname.
2159
2160 To specify proxy on a unix domain socket, use localhost for host, e.g.
2161 \&"socks4a://localhost/path/to/socket.sock"
2162@@ -4476,9 +4501,9 @@ Example:
2163
2164 See also \fI\-\-socks4\fP, \fI\-\-socks5\fP and \fI\-\-socks5\-hostname\fP.
2165 .IP "\-\-socks5\-basic"
2166-Tells curl to use username/password authentication when connecting to a SOCKS5
2167-proxy. The username/password authentication is enabled by default. Use
2168-\fI\-\-socks5\-gssapi\fP to force GSS\-API authentication to SOCKS5 proxies.
2169+Use username/password authentication when connecting to a SOCKS5 proxy. The
2170+username/password authentication is enabled by default. Use \fI\-\-socks5\-gssapi\fP to
2171+force GSS\-API authentication to SOCKS5 proxies.
2172
2173 Providing --socks5-basic multiple times has no extra effect.
2174
2175@@ -4504,8 +4529,7 @@ Example:
2176
2177 See also \fI\-\-socks5\fP.
2178 .IP "\-\-socks5\-gssapi\-service <name>"
2179-The default service name for a socks server is \fBrcmd/server\-fqdn\fP. This option
2180-allows you to change it.
2181+Set the service name for a socks server. Default is \fBrcmd/server\-fqdn\fP.
2182
2183 If --socks5-gssapi-service is provided several times, the last set value is used.
2184
2185@@ -4516,10 +4540,10 @@ Example:
2186
2187 See also \fI\-\-socks5\fP.
2188 .IP "\-\-socks5\-gssapi"
2189-Tells curl to use GSS\-API authentication when connecting to a SOCKS5 proxy.
2190-The GSS\-API authentication is enabled by default (if curl is compiled with
2191-GSS\-API support). Use \fI\-\-socks5\-basic\fP to force username/password authentication
2192-to SOCKS5 proxies.
2193+Use GSS\-API authentication when connecting to a SOCKS5 proxy. The GSS\-API
2194+authentication is enabled by default (if curl is compiled with GSS\-API
2195+support). Use \fI\-\-socks5\-basic\fP to force username/password authentication to
2196+SOCKS5 proxies.
2197
2198 Providing --socks5-gssapi multiple times has no extra effect.
2199 Disable it again with \-\-no-socks5-gssapi.
2200@@ -4531,7 +4555,7 @@ Example:
2201
2202 See also \fI\-\-socks5\fP. Added in 7.55.0.
2203 .IP "\-\-socks5\-hostname <host[:port]>"
2204-Use the specified SOCKS5 proxy (and let the proxy resolve the host name). If
2205+Use the specified SOCKS5 proxy (and let the proxy resolve the hostname). If
2206 the port number is not specified, it is assumed at port 1080.
2207
2208 To specify proxy on a unix domain socket, use localhost for host, e.g.
2209@@ -4557,7 +4581,7 @@ Example:
2210
2211 See also \fI\-\-socks5\fP and \fI\-\-socks4a\fP.
2212 .IP "\-\-socks5 <host[:port]>"
2213-Use the specified SOCKS5 proxy \- but resolve the host name locally. If the
2214+Use the specified SOCKS5 proxy \- but resolve the hostname locally. If the
2215 port number is not specified, it is assumed at port 1080.
2216
2217 To specify proxy on a unix domain socket, use localhost for host, e.g.
2218@@ -4614,10 +4638,9 @@ Example:
2219
2220 See also \fI-Y, \-\-speed\-limit\fP and \fI\-\-limit\-rate\fP.
2221 .IP "\-\-ssl\-allow\-beast"
2222-(TLS) This option tells curl to not work around a security flaw in the SSL3 and
2223-TLS1.0 protocols known as BEAST. If this option is not used, the SSL layer may
2224-use workarounds known to cause interoperability problems with some older SSL
2225-implementations.
2226+(TLS) Do not work around a security flaw in the SSL3 and TLS1.0 protocols known as
2227+BEAST. If this option is not used, the SSL layer may use workarounds known to
2228+cause interoperability problems with some older SSL implementations.
2229
2230 \fBWARNING\fP: this option loosens the SSL security, and by using this flag you
2231 ask for exactly that.
2232@@ -4632,10 +4655,10 @@ Example:
2233
2234 See also \fI\-\-proxy\-ssl\-allow\-beast\fP and \fI-k, \-\-insecure\fP.
2235 .IP "\-\-ssl\-auto\-client\-cert"
2236-(TLS) (Schannel) Tell libcurl to automatically locate and use a client certificate
2237-for authentication, when requested by the server. Since the server can request
2238-any certificate that supports client authentication in the OS certificate
2239-store it could be a privacy violation and unexpected.
2240+(TLS) (Schannel) Automatically locate and use a client certificate for
2241+authentication, when requested by the server. Since the server can request any
2242+certificate that supports client authentication in the OS certificate store it
2243+could be a privacy violation and unexpected.
2244
2245 Providing --ssl-auto-client-cert multiple times has no extra effect.
2246 Disable it again with \-\-no-ssl-auto-client-cert.
2247@@ -4647,9 +4670,8 @@ Example:
2248
2249 See also \fI\-\-proxy\-ssl\-auto\-client\-cert\fP. Added in 7.77.0.
2250 .IP "\-\-ssl\-no\-revoke"
2251-(TLS) (Schannel) This option tells curl to disable certificate revocation checks.
2252-WARNING: this option loosens the SSL security, and by using this flag you ask
2253-for exactly that.
2254+(TLS) (Schannel) Disable certificate revocation checks. WARNING: this option loosens
2255+the SSL security, and by using this flag you ask for exactly that.
2256
2257 Providing --ssl-no-revoke multiple times has no extra effect.
2258 Disable it again with \-\-no-ssl-no-revoke.
2259@@ -4672,7 +4694,7 @@ This option is unnecessary if you use a URL scheme that in itself implies
2260 immediate and implicit use of TLS, like for FTPS, IMAPS, POP3S, SMTPS and
2261 LDAPS. Such a transfer always fails if the TLS handshake does not work.
2262
2263-This option was formerly known as \--ftp\-ssl\-reqd.
2264+This option was formerly known as \fI\-\-ftp\-ssl\-reqd\fP.
2265
2266 Providing --ssl-reqd multiple times has no extra effect.
2267 Disable it again with \-\-no-ssl-reqd.
2268@@ -4684,9 +4706,8 @@ Example:
2269
2270 See also \fI\-\-ssl\fP and \fI-k, \-\-insecure\fP.
2271 .IP "\-\-ssl\-revoke\-best\-effort"
2272-(TLS) (Schannel) This option tells curl to ignore certificate revocation checks when
2273-they failed due to missing/offline distribution points for the revocation check
2274-lists.
2275+(TLS) (Schannel) Ignore certificate revocation checks when they failed due to
2276+missing/offline distribution points for the revocation check lists.
2277
2278 Providing --ssl-revoke-best-effort multiple times has no extra effect.
2279 Disable it again with \-\-no-ssl-revoke-best-effort.
2280@@ -4711,7 +4732,7 @@ OpenLDAP backend and ignored by the generic ldap backend.
2281 Please note that a server may close the connection if the negotiation does
2282 not succeed.
2283
2284-This option was formerly known as \--ftp\-ssl. That option
2285+This option was formerly known as \fI\-\-ftp\-ssl\fP. That option
2286 name can still be used but might be removed in a future version.
2287
2288 Providing --ssl multiple times has no extra effect.
2289@@ -4748,7 +4769,7 @@ Example:
2290
2291 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.
2292 .IP "\-\-stderr <file>"
2293-Redirect all writes to stderr to the specified file instead. If the file name
2294+Redirect all writes to stderr to the specified file instead. If the filename
2295 is a plain \(aq\-\(aq, it is instead written to stdout.
2296
2297 This option is global and does not need to be specified for each use of --next.
2298@@ -4762,8 +4783,8 @@ Example:
2299
2300 See also \fI-v, \-\-verbose\fP and \fI-s, \-\-silent\fP.
2301 .IP "\-\-styled\-output"
2302-Enables the automatic use of bold font styles when writing HTTP headers to the
2303-terminal. Use \--no\-styled\-output to switch them off.
2304+Enable automatic use of bold font styles when writing HTTP headers to the
2305+terminal. Use \fI\-\-no\-styled\-output\fP to switch them off.
2306
2307 Styled output requires a terminal that supports bold fonts. This feature is
2308 not present on curl for Windows due to lack of this capability.
2309@@ -4845,9 +4866,9 @@ Example:
2310
2311 See also \fI-K, \-\-config\fP.
2312 .IP "\-\-tftp\-blksize <value>"
2313-(TFTP) Set the TFTP \fBBLKSIZE\fP option (must be >512). This is the block size that
2314-curl tries to use when transferring data to or from a TFTP server. By
2315-default 512 bytes are used.
2316+(TFTP) Set the TFTP \fBBLKSIZE\fP option (must be 512 or larger). This is the block
2317+size that curl tries to use when transferring data to or from a TFTP
2318+server. By default 512 bytes are used.
2319
2320 If --tftp-blksize is provided several times, the last set value is used.
2321
2322@@ -4858,11 +4879,9 @@ Example:
2323
2324 See also \fI\-\-tftp\-no\-options\fP.
2325 .IP "\-\-tftp\-no\-options"
2326-(TFTP) Tells curl not to send TFTP options requests.
2327-
2328-This option improves interop with some legacy servers that do not acknowledge
2329-or properly implement TFTP options. When this option is used \fI\-\-tftp\-blksize\fP is
2330-ignored.
2331+(TFTP) Do not to send TFTP options requests. This improves interop with some legacy
2332+servers that do not acknowledge or properly implement TFTP options. When this
2333+option is used \fI\-\-tftp\-blksize\fP is ignored.
2334
2335 Providing --tftp-no-options multiple times has no extra effect.
2336 Disable it again with \-\-no-tftp-no-options.
2337@@ -4875,10 +4894,10 @@ Example:
2338 See also \fI\-\-tftp\-blksize\fP.
2339 .IP "\-z, \-\-time\-cond <time>"
2340 (HTTP FTP) Request a file that has been modified later than the given time and date, or
2341-one that has been modified before that time. The <date expression> can be all
2342-sorts of date strings or if it does not match any internal ones, it is taken as
2343-a filename and tries to get the modification date (mtime) from <file>
2344-instead. See the \fIcurl_getdate(3)\fP man pages for date expression details.
2345+one that has been modified before that time. The date expression can be all
2346+sorts of date strings or if it does not match any internal ones, it is treated
2347+as a filename and curl tries to get the modification date (mtime) from that
2348+file instead. See the \fIcurl_getdate(3)\fP man pages for date expression details.
2349
2350 Start the date expression with a dash (\-) to make it request for a document
2351 that is older than the given date/time, default is a document that is newer
2352@@ -4926,7 +4945,7 @@ Examples:
2353 .fi
2354
2355 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.
2356-.IP "\-\-tls13\-ciphers <ciphersuite list>"
2357+.IP "\-\-tls13\-ciphers <list>"
2358 (TLS) Specifies which cipher suites to use in the connection if it negotiates TLS
2359 1.3. The list of ciphers suites must specify valid ciphers. Read up on TLS 1.3
2360 cipher suite details on this URL:
2361@@ -5051,8 +5070,8 @@ Example:
2362
2363 See also \fI\-\-tlsv1.2\fP and \fI\-\-tls\-max\fP. Added in 7.52.0.
2364 .IP "\-1, \-\-tlsv1"
2365-(TLS) Tells curl to use at least TLS version 1.x when negotiating with a remote TLS
2366-server. That means TLS version 1.0 or higher
2367+(TLS) Use at least TLS version 1.x when negotiating with a remote TLS server. That
2368+means TLS version 1.0 or higher
2369
2370 Providing --tlsv1 multiple times has no extra effect.
2371
2372@@ -5076,8 +5095,8 @@ Example:
2373
2374 See also \fI\-\-compressed\fP.
2375 .IP "\-\-trace\-ascii <file>"
2376-Enables a full trace dump of all incoming and outgoing data, including
2377-descriptive information, to the given output file. Use "\-" as filename to have
2378+Save a full trace dump of all incoming and outgoing data, including
2379+descriptive information, in the given output file. Use "\-" as filename to have
2380 the output sent to stdout.
2381
2382 This is similar to \fI\-\-trace\fP, but leaves out the hex part and only shows the
2383@@ -5085,7 +5104,7 @@ ASCII part of the dump. It makes smaller output that might be easier to read
2384 for untrained humans.
2385
2386 Note that verbose output of curl activities and network traffic might contain
2387-sensitive data, including user names, credentials or secret data content. Be
2388+sensitive data, including usernames, credentials or secret data content. Be
2389 aware and be careful when sharing trace logs with others.
2390
2391 This option is global and does not need to be specified for each use of --next.
2392@@ -5103,8 +5122,8 @@ Set configuration for trace output. A comma\-separated list of components where
2393 detailed output can be made available from. Names are case\-insensitive.
2394 Specify \(aqall\(aq to enable all trace components.
2395
2396-In addition to trace component names, specify "ids" and "time" to
2397-avoid extra \fI\-\-trace\-ids\fP or \fI\-\-trace\-time\fP parameters.
2398+In addition to trace component names, specify "ids" and "time" to avoid extra
2399+\fI\-\-trace\-ids\fP or \fI\-\-trace\-time\fP parameters.
2400
2401 See the \fIcurl_global_trace(3)\fP man page for more details.
2402
2403@@ -5117,7 +5136,7 @@ Example:
2404 curl --trace-config ids,http/2 https://example.com
2405 .fi
2406
2407-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.
2408+See also \fI-v, \-\-verbose\fP and \fI\-\-trace\fP. Added in 8.3.0.
2409 .IP "\-\-trace\-ids"
2410 Prepends the transfer and connection identifiers to each trace or verbose line that curl displays.
2411
2412@@ -5147,13 +5166,13 @@ Example:
2413
2414 See also \fI\-\-trace\fP and \fI-v, \-\-verbose\fP.
2415 .IP "\-\-trace <file>"
2416-Enables a full trace dump of all incoming and outgoing data, including
2417-descriptive information, to the given output file. Use "\-" as filename to have
2418+Save a full trace dump of all incoming and outgoing data, including
2419+descriptive information, in the given output file. Use "\-" as filename to have
2420 the output sent to stdout. Use "%" as filename to have the output sent to
2421 stderr.
2422
2423 Note that verbose output of curl activities and network traffic might contain
2424-sensitive data, including user names, credentials or secret data content. Be
2425+sensitive data, including usernames, credentials or secret data content. Be
2426 aware and be careful when sharing trace logs with others.
2427
2428 This option is global and does not need to be specified for each use of --next.
2429@@ -5178,28 +5197,28 @@ Example:
2430
2431 See also \fI\-\-abstract\-unix\-socket\fP.
2432 .IP "\-T, \-\-upload\-file <file>"
2433-This transfers the specified local file to the remote URL.
2434+Upload the specified local file to the remote URL.
2435
2436 If there is no file part in the specified URL, curl appends the local file
2437 name to the end of the URL before the operation starts. You must use a
2438 trailing slash (/) on the last directory to prove to curl that there is no
2439-file name or curl thinks that your last directory name is the remote file name
2440+filename or curl thinks that your last directory name is the remote filename
2441 to use.
2442
2443-When putting the local file name at the end of the URL, curl ignores what is
2444-on the left side of any slash (/) or backslash (\\) used in the file name and
2445-only appends what is on the right side of the rightmost such character.
2446+When putting the local filename at the end of the URL, curl ignores what is on
2447+the left side of any slash (/) or backslash (\\) used in the filename and only
2448+appends what is on the right side of the rightmost such character.
2449
2450-Use the file name "\-" (a single dash) to use stdin instead of a given file.
2451-Alternately, the file name "." (a single period) may be specified instead of
2452+Use the filename "\-" (a single dash) to use stdin instead of a given file.
2453+Alternately, the filename "." (a single period) may be specified instead of
2454 \&"\-" to use stdin in non\-blocking mode to allow reading server output while
2455 stdin is being uploaded.
2456
2457-If this option is used with a HTTP(S) URL, the PUT method is used.
2458+If this option is used with an HTTP(S) URL, the PUT method is used.
2459
2460 You can specify one \fI\-T, \-\-upload\-file\fP for each URL on the command line. Each
2461 \fI\-T, \-\-upload\-file\fP + URL pair specifies what to upload and to where. curl also
2462-supports "globbing" of the \fI\-T, \-\-upload\-file\fP argument, meaning that you can upload
2463+supports globbing of the \fI\-T, \-\-upload\-file\fP argument, meaning that you can upload
2464 multiple files to a single URL by using the same URL globbing style supported
2465 in the URL.
2466
2467@@ -5219,9 +5238,9 @@ Examples:
2468
2469 See also \fI-G, \-\-get\fP, \fI-I, \-\-head\fP, \fI-X, \-\-request\fP and \fI-d, \-\-data\fP.
2470 .IP "\-\-url\-query <data>"
2471-(all) This option adds a piece of data, usually a name + value pair, to the end of
2472-the URL query part. The syntax is identical to that used for \fI\-\-data\-urlencode\fP
2473-with one extension:
2474+(all) Add a piece of data, usually a name + value pair, to the end of the URL query
2475+part. The syntax is identical to that used for \fI\-\-data\-urlencode\fP with one
2476+extension:
2477
2478 If the argument starts with a \(aq+\(aq (plus), the rest of the string is provided
2479 as\-is unencoded.
2480@@ -5242,8 +5261,7 @@ Examples:
2481
2482 See also \fI\-\-data\-urlencode\fP and \fI-G, \-\-get\fP. Added in 7.87.0.
2483 .IP "\-\-url <url>"
2484-Specify a URL to fetch. This option is mostly handy when you want to specify
2485-URL(s) in a config file.
2486+Specify a URL to fetch.
2487
2488 If the given URL is missing a scheme name (such as "http://" or "ftp://" etc)
2489 then curl makes a guess based on the host. If the outermost subdomain name
2490@@ -5255,7 +5273,7 @@ including the scheme, or disabled by setting a default protocol (added in
2491 To control where this URL is written, use the \fI\-o, \-\-output\fP or the \fI\-O, \-\-remote\-name\fP
2492 options.
2493
2494-\fBWARNING\fP: On Windows, particular file:// accesses can be converted to
2495+\fBWARNING\fP: On Windows, particular "file://" accesses can be converted to
2496 network accesses by the operating system. Beware!
2497
2498 --url can be used several times in a command line
2499@@ -5267,9 +5285,9 @@ Example:
2500
2501 See also \fI-:, \-\-next\fP and \fI-K, \-\-config\fP.
2502 .IP "\-B, \-\-use\-ascii"
2503-(FTP LDAP) Enable ASCII transfer. For FTP, this can also be enforced by using a URL that
2504-ends with ";type=A". This option causes data sent to stdout to be in text mode
2505-for win32 systems.
2506+(FTP LDAP) Enable ASCII transfer mode. For FTP, this can also be enforced by using a URL
2507+that ends with ";type=A". This option causes data sent to stdout to be in text
2508+mode for win32 systems.
2509
2510 Providing --use-ascii multiple times has no extra effect.
2511 Disable it again with \-\-no-use-ascii.
2512@@ -5298,13 +5316,13 @@ Example:
2513
2514 See also \fI-H, \-\-header\fP and \fI\-\-proxy\-header\fP.
2515 .IP "\-u, \-\-user <user:password>"
2516-Specify the user name and password to use for server authentication. Overrides
2517+Specify the username and password to use for server authentication. Overrides
2518 \fI\-n, \-\-netrc\fP and \fI\-\-netrc\-optional\fP.
2519
2520-If you simply specify the user name, curl prompts for a password.
2521+If you simply specify the username, curl prompts for a password.
2522
2523-The user name and passwords are split up on the first colon, which makes it
2524-impossible to use a colon in the user name with this option. The password can,
2525+The username and passwords are split up on the first colon, which makes it
2526+impossible to use a colon in the username with this option. The password can,
2527 still.
2528
2529 On systems where it works, curl hides the given option argument from process
2530@@ -5314,22 +5332,21 @@ before cleared. Such sensitive data should be retrieved from a file instead or
2531 similar and never used in clear text in a command line.
2532
2533 When using Kerberos V5 with a Windows based server you should include the
2534-Windows domain name in the user name, in order for the server to successfully
2535+Windows domain name in the username, in order for the server to successfully
2536 obtain a Kerberos Ticket. If you do not, then the initial authentication
2537 handshake may fail.
2538
2539-When using NTLM, the user name can be specified simply as the user name,
2540-without the domain, if there is a single domain and forest in your setup
2541-for example.
2542+When using NTLM, the username can be specified simply as the username, without
2543+the domain, if there is a single domain and forest in your setup for example.
2544
2545 To specify the domain name use either Down\-Level Logon Name or UPN (User
2546 Principal Name) formats. For example, EXAMPLE\\user and user@example.com
2547 respectively.
2548
2549 If you use a Windows SSPI\-enabled curl binary and perform Kerberos V5,
2550-Negotiate, NTLM or Digest authentication then you can tell curl to select
2551-the user name and password from your environment by specifying a single colon
2552-with this option: "\-u :".
2553+Negotiate, NTLM or Digest authentication then you can tell curl to select the
2554+username and password from your environment by specifying a single colon with
2555+this option: "\-u :".
2556
2557 If --user is provided several times, the last set value is used.
2558
2559@@ -5341,21 +5358,21 @@ Example:
2560 See also \fI-n, \-\-netrc\fP and \fI-K, \-\-config\fP.
2561 .IP "\-\-variable <[%]name=text/@file>"
2562 Set a variable with "name=content" or "name@file" (where "file" can be stdin
2563-if set to a single dash (\-)). The name is a case sensitive identifier that
2564+if set to a single dash ("\-")). The name is a case sensitive identifier that
2565 must consist of no other letters than a\-z, A\-Z, 0\-9 or underscore. The
2566 specified content is then associated with this identifier.
2567
2568 Setting the same variable name again overwrites the old contents with the new.
2569
2570 The contents of a variable can be referenced in a later command line option
2571-when that option name is prefixed with "\--expand\-", and the name is used as
2572-\&"{{name}}" (without the quotes).
2573+when that option name is prefixed with "\fI\-\-expand\-\fP", and the name is used as
2574+\&"{{name}}".
2575
2576 \fI\-\-variable\fP can import environment variables into the name space. Opt to either
2577 require the environment variable to be set or provide a default value for the
2578 variable in case it is not already set.
2579
2580-\fI\-\-variable\fP %name imports the variable called \(aqname\(aq but exits with an error if
2581+\fI\-\-variable\fP %name imports the variable called "name" but exits with an error if
2582 that environment variable is not already set. To provide a default value if
2583 the environment variable is not set, use \fI\-\-variable\fP %name=content or
2584 \fI\-\-variable\fP %name@content. Note that on some systems \- but not all \-
2585@@ -5391,10 +5408,9 @@ Example:
2586 See also \fI-K, \-\-config\fP. Added in 8.3.0.
2587 .IP "\-v, \-\-verbose"
2588 Makes curl verbose during the operation. Useful for debugging and seeing
2589-what\(aqs going on "under the hood". A line starting with \(aq>\(aq means "header data"
2590-sent by curl, \(aq<\(aq means "header data" received by curl that is hidden in
2591-normal cases, and a line starting with \(aq*\(aq means additional info provided by
2592-curl.
2593+what\(aqs going on under the hood. A line starting with > means header data sent
2594+by curl, < means header data received by curl that is hidden in normal cases,
2595+and a line starting with * means additional info provided by curl.
2596
2597 If you only want HTTP headers in the output, \fI\-i, \-\-include\fP or \fI\-D, \-\-dump\-header\fP might
2598 be more suitable options.
2599@@ -5403,7 +5419,7 @@ If you think this option still does not give you enough details, consider using
2600 \fI\-\-trace\fP or \fI\-\-trace\-ascii\fP instead.
2601
2602 Note that verbose output of curl activities and network traffic might contain
2603-sensitive data, including user names, credentials or secret data content. Be
2604+sensitive data, including usernames, credentials or secret data content. Be
2605 aware and be careful when sharing trace logs with others.
2606
2607 This option is global and does not need to be specified for each use of --next.
2608@@ -5504,10 +5520,10 @@ Example:
2609 See also \fI-h, \-\-help\fP and \fI-M, \-\-manual\fP.
2610 .IP "\-w, \-\-write\-out <format>"
2611 Make curl display information on stdout after a completed transfer. The format
2612-is a string that may contain plain text mixed with any number of
2613-variables. The format can be specified as a literal "string", or you can have
2614-curl read the format from a file with "@filename" and to tell curl to read the
2615-format from stdin you write "@\-".
2616+is a string that may contain plain text mixed with any number of variables.
2617+The format can be specified as a literal "string", or you can have curl read
2618+the format from a file with "@filename" and to tell curl to read the format
2619+from stdin you write "@\-".
2620
2621 The variables present in the output format are substituted by the value or
2622 text that curl thinks fit, as described below. All variables are specified as
2623@@ -5524,18 +5540,24 @@ colon). The header contents are exactly as sent over the network, with leading
2624 and trailing whitespace trimmed (added in 7.84.0).
2625
2626 Select a specific target destination file to write the output to, by using
2627-\fI%output{name}\fP (added in curl 8.3.0) where \fIname\fP is the full file name. The
2628+\fI%output{name}\fP (added in curl 8.3.0) where \fIname\fP is the full filename. The
2629 output following that instruction is then written to that file. More than one
2630 \fI%output{}\fP instruction can be specified in the same write\-out argument. If
2631-the file name cannot be created, curl leaves the output destination to the one
2632+the filename cannot be created, curl leaves the output destination to the one
2633 used prior to the \fI%output{}\fP instruction. Use \fI%output{>>name}\fP to append
2634 data to an existing file.
2635
2636-\fBNOTE:\fP
2637-In Windows the %\-symbol is a special symbol used to expand environment
2638-variables. In batch files all occurrences of % must be doubled when using this
2639-option to properly escape. If this option is used at the command prompt then
2640-the % cannot be escaped and unintended expansion is possible.
2641+This output is done independently of if the file transfer was successful or
2642+not.
2643+
2644+If the specified action or output specified with this option fails in any way,
2645+it does not make curl return a (different) error.
2646+
2647+\fBNOTE:\fP On Windows, the %\-symbol is a special symbol used to expand
2648+environment variables. In batch files, all occurrences of % must be doubled
2649+when using this option to properly escape. If this option is used at the
2650+command prompt then the % cannot be escaped and unintended expansion is
2651+possible.
2652
2653 The variables available are:
2654 .RS
2655@@ -5550,9 +5572,9 @@ The error message. (Added in 7.75.0)
2656 The numerical exit code of the transfer. (Added in 7.75.0)
2657 .IP `filename_effective`
2658 The ultimate filename that curl writes out to. This is only meaningful if curl
2659-is told to write to a file with the \fI\-O, \-\-remote\-name\fP or \fI\-o, \-\-output\fP
2660-option. It\(aqs most useful in combination with the \fI\-J, \-\-remote\-header\-name\fP
2661-option.
2662+is told to write to a file with the \fI\-O, \-\-remote\-name\fP or \fI\-o, \-\-output\fP option. It is
2663+most useful in combination with the \fI\-J, \-\-remote\-header\-name\fP option. (Added in
2664+7.26.0)
2665 .IP `ftp_entry_path`
2666 The initial path curl ended up in when logging on to the remote FTP
2667 server.
2668@@ -5598,6 +5620,10 @@ The rest of the output is only shown if the transfer returned a non\-zero error.
2669 .IP `proxy_ssl_verify_result`
2670 The result of the HTTPS proxy\(aqs SSL peer certificate verification that was
2671 requested. 0 means the verification was successful. (Added in 7.52.0)
2672+.IP `proxy_used`
2673+Returns 1 if the previous transfer used a proxy, otherwise 0. Useful to for
2674+example determine if a "NOPROXY" pattern matched the hostname or not. (Added
2675+in 8.7.0)
2676 .IP `redirect_url`
2677 When an HTTP request was made without \fI\-L, \-\-location\fP to follow redirects (or when
2678 \fI\-\-max\-redirs\fP is met), this variable shows the actual URL a redirect
2679@@ -5728,11 +5754,11 @@ Example:
2680
2681 See also \fI-v, \-\-verbose\fP and \fI-I, \-\-head\fP.
2682 .IP "\-\-xattr"
2683-When saving output to a file, this option tells curl to store certain file
2684-metadata in extended file attributes. Currently, the URL is stored in the
2685-\&"xdg.origin.url" attribute and, for HTTP, the content type is stored in the
2686-\&"mime_type" attribute. If the file system does not support extended
2687-attributes, a warning is issued.
2688+When saving output to a file, tell curl to store file metadata in extended
2689+file attributes. Currently, the URL is stored in the "xdg.origin.url"
2690+attribute and, for HTTP, the content type is stored in the "mime_type"
2691+attribute. If the file system does not support extended attributes, a warning
2692+is issued.
2693
2694 Providing --xattr multiple times has no extra effect.
2695 Disable it again with \-\-no-xattr.
2696@@ -5765,9 +5791,9 @@ SMTP, LDAP, etc.
2697 .IP "`ALL_PROXY` [protocol://]<host>[:port]"
2698 Sets the proxy server to use if no protocol\-specific proxy is set.
2699 .IP "`NO_PROXY` <comma-separated list of hosts/domains>"
2700-list of host names that should not go through any proxy. If set to an asterisk
2701-\(aq*\(aq only, it matches all hosts. Each name in this list is matched as either
2702-a domain name which contains the hostname, or the hostname itself.
2703+list of hostnames that should not go through any proxy. If set to an asterisk
2704+\(aq*\(aq only, it matches all hosts. Each name in this list is matched as either a
2705+domain name which contains the hostname, or the hostname itself.
2706
2707 This environment variable disables use of the proxy even when specified with
2708 the \fI\-x, \-\-proxy\fP option. That is
2709@@ -5786,7 +5812,7 @@ http://somewhere.example.com
2710
2711 accesses the target URL through the proxy.
2712
2713-The list of host names can also be include numerical IP addresses, and IPv6
2714+The list of hostnames can also be include numerical IP addresses, and IPv6
2715 versions should then be given without enclosing brackets.
2716
2717 IP addresses can be specified using CIDR notation: an appended slash and
2718@@ -5832,8 +5858,8 @@ if Schannel is used as the TLS backend.
2719 .IP "`SSL_CERT_FILE` <path>"
2720 If set, it is used as the \fI\-\-cacert\fP value. This environment variable is ignored
2721 if Schannel is used as the TLS backend.
2722-.IP "`SSLKEYLOGFILE` <file name>"
2723-If you set this environment variable to a file name, curl stores TLS secrets
2724+.IP "`SSLKEYLOGFILE` <filename>"
2725+If you set this environment variable to a filename, curl stores TLS secrets
2726 from its connections in that file when invoked to enable you to analyze the
2727 TLS traffic in real time using network analyzing tools such as Wireshark. This
2728 works with the following TLS backends: OpenSSL, libressl, BoringSSL, GnuTLS
2729@@ -6000,7 +6026,7 @@ Sending the data requires a rewind that failed.
2730 .IP 66
2731 Failed to initialize SSL Engine.
2732 .IP 67
2733-The user name, password, or similar was not accepted and curl failed to log in.
2734+The username, password, or similar was not accepted and curl failed to log in.
2735 .IP 68
2736 File not found on TFTP server.
2737 .IP 69
2738@@ -6061,6 +6087,8 @@ Proxy handshake error.
2739 A client\-side certificate is required to complete the TLS handshake.
2740 .IP 99
2741 Poll or select returned fatal error.
2742+.IP 100
2743+A value or data field grew larger than allowed.
2744 .IP XX
2745 More error codes might appear here in future releases. The existing ones are
2746 meant to never change.
+3,
-3
1@@ -77,7 +77,7 @@
2 #define HAVE_FSEEKO 1
3 #define HAVE_FSETXATTR 1
4 #define HAVE_FSETXATTR_5 1
5-/* #undef HAVE_FSETXATTR_6 */
6+/* #undef HAVE_FSETXATTR_5 */
7 #define HAVE_FTRUNCATE 1
8 #define HAVE_GETADDRINFO 1
9 #define HAVE_GETADDRINFO_THREADSAFE 1
10@@ -129,6 +129,7 @@
11 /* #undef HAVE_LIBBROTLIDEC */
12 #define HAVE_LIBGEN_H 1
13 /* #undef HAVE_LIBIDN2 */
14+/* #undef HAVE_LIBPSL_H */
15 /* #undef HAVE_LIBRESSL */
16 /* #undef HAVE_LIBRTMP_RTMP_H */
17 /* #undef HAVE_LIBSSH */
18@@ -282,7 +283,7 @@
19 /* #undef USE_LIBRTMP */
20 /* #undef USE_LIBSSH */
21 /* #undef USE_LIBSSH2 */
22-/* #undef USE_MANUAL */
23+#define USE_MANUAL 1
24 /* #undef USE_MBEDTLS */
25 /* #undef USE_MSH3 */
26 /* #undef USE_NGHTTP2 */
27@@ -305,7 +306,6 @@
28 /* #undef USE_THREADS_WIN32 */
29 /* #undef USE_TLS_SRP */
30 #define USE_UNIX_SOCKETS 1
31-/* enable websockets support */
32 /* #undef USE_WEBSOCKETS */
33 /* #undef USE_WIN32_CRYPTO */
34 /* #undef USE_WIN32_IDN */
+24,
-22
1@@ -44,35 +44,36 @@ lib('libcurl.a', [[
2 curl_endian.c curl_fnmatch.c curl_get_line.c curl_gethostname.c
3 curl_gssapi.c curl_memrchr.c curl_multibyte.c curl_ntlm_core.c
4 curl_ntlm_wb.c curl_path.c curl_range.c curl_rtmp.c curl_sasl.c
5- curl_sspi.c curl_threads.c curl_trc.c dict.c doh.c dynbuf.c
6- dynhds.c easy.c easygetopt.c easyoptions.c escape.c file.c
7- fileinfo.c fopen.c formdata.c ftp.c ftplistparser.c getenv.c
8- getinfo.c gopher.c hash.c headers.c hmac.c hostasyn.c hostip.c
9- hostip4.c hostip6.c hostsyn.c hsts.c http.c http1.c http2.c
10- http_aws_sigv4.c http_chunks.c http_digest.c http_negotiate.c
11- http_ntlm.c http_proxy.c idn.c if2ip.c imap.c inet_ntop.c
12- inet_pton.c krb5.c ldap.c llist.c macos.c md4.c md5.c memdebug.c
13- mime.c mprintf.c mqtt.c multi.c netrc.c nonblock.c noproxy.c
14- openldap.c parsedate.c pingpong.c pop3.c progress.c psl.c rand.c
15- rename.c rtsp.c select.c sendf.c setopt.c sha256.c share.c
16- slist.c smb.c smtp.c socketpair.c socks.c socks_gssapi.c
17- socks_sspi.c speedcheck.c splay.c strcase.c strdup.c strerror.c
18- strtok.c strtoofft.c system_win32.c telnet.c tftp.c timediff.c
19- timeval.c transfer.c url.c urlapi.c version.c version_win32.c
20- warnless.c ws.c
21+ curl_sha512_256.c curl_sspi.c curl_threads.c curl_trc.c cw-out.c
22+ dict.c doh.c dynbuf.c dynhds.c easy.c easygetopt.c easyoptions.c
23+ escape.c file.c fileinfo.c fopen.c formdata.c ftp.c
24+ ftplistparser.c getenv.c getinfo.c gopher.c hash.c headers.c
25+ hmac.c hostasyn.c hostip.c hostip4.c hostip6.c hostsyn.c hsts.c
26+ http.c http1.c http2.c http_aws_sigv4.c http_chunks.c
27+ http_digest.c http_negotiate.c http_ntlm.c http_proxy.c idn.c
28+ if2ip.c imap.c inet_ntop.c inet_pton.c krb5.c ldap.c llist.c
29+ macos.c md4.c md5.c memdebug.c mime.c mprintf.c mqtt.c multi.c
30+ netrc.c nonblock.c noproxy.c openldap.c parsedate.c pingpong.c
31+ pop3.c progress.c psl.c rand.c rename.c request.c rtsp.c
32+ select.c sendf.c setopt.c sha256.c share.c slist.c smb.c smtp.c
33+ socketpair.c socks.c socks_gssapi.c socks_sspi.c speedcheck.c
34+ splay.c strcase.c strdup.c strerror.c strtok.c strtoofft.c
35+ system_win32.c telnet.c tftp.c timediff.c timeval.c transfer.c
36+ url.c urlapi.c version.c version_win32.c warnless.c ws.c
37 vauth/(
38- cleartext.c cram.c digest.c digest_sspi.c
39- gsasl.c krb5_gssapi.c krb5_sspi.c ntlm.c
40- ntlm_sspi.c oauth2.c spnego_gssapi.c
41+ cleartext.c cram.c digest.c digest_sspi.c gsasl.c krb5_gssapi.c
42+ krb5_sspi.c ntlm.c ntlm_sspi.c oauth2.c spnego_gssapi.c
43 spnego_sspi.c vauth.c
44 )
45 vtls/(
46 bearssl.c gtls.c hostcheck.c keylog.c mbedtls.c
47 mbedtls_threadlock.c openssl.c rustls.c schannel.c
48- schannel_verify.c sectransp.c vtls.c wolfssl.c
49- x509asn1.c
50+ schannel_verify.c sectransp.c vtls.c wolfssl.c x509asn1.c
51 )
52- vquic/(curl_msh3.c curl_ngtcp2.c curl_quiche.c vquic.c)
53+ vquic/(
54+ curl_msh3.c curl_ngtcp2.c curl_osslq.c curl_quiche.c vquic.c
55+ vquic-tls.c
56+ )
57 vssh/(libssh.c libssh2.c wolfssh.c)
58 )
59 $builddir/pkg/bearssl/libbearssl.a
60@@ -102,6 +103,7 @@ exe('curl', [[
61 tool_getpass.c
62 tool_help.c
63 tool_helpers.c
64+ tool_hugehelp.c
65 tool_ipfs.c
66 tool_libinfo.c
67 tool_listhelp.c
+1,
-1
1@@ -1 +1 @@
2-9c6db808160015f30f3c656c0dec125feb9dc00753596bf858a272b5dd8dc398 curl-8.6.0.tar.gz
3+f91249c87f68ea00cf27c44fdfa5a78423e41e71b7d408e5901a9896d905c495 curl-8.7.1.tar.gz
+1,
-1
1@@ -1 +1 @@
2-url = "https://curl.se/download/curl-8.6.0.tar.gz"
3+url = "https://curl.se/download/curl-8.7.1.tar.gz"
+1,
-1
1@@ -1 +1 @@
2-8.6.0 r0
3+8.7.1 r0