romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-05-30 04:27:30 +03:00
Code Issues Projects Releases Packages Wiki Activity

page-header: minor wording polish in the URL segment

Browse source 
Closes #11217
This commit is contained in:
Daniel Stenberg 2023-05-29 11:44:55 +02:00
parent 47e4fcf7b9
commit b62b5de7eb
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
1 changed files with 12 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

27
docs/cmdline-opts/page-header
View file

@ -66,8 +66,9 @@ other:
"http://example.com/archive[1996-1999]/vol[1-4]/part{a,b,c}.html"
You can specify any amount of URLs on the command line. They will be fetched
in a sequential manner in the specified order. You can specify command line
options and URLs mixed and in any order on the command line.
in a sequential manner in the specified order unless you use --parallel. You
can specify command line options and URLs mixed and in any order on the
command line.
You can specify a step counter for the ranges to get every Nth number or
letter:
@ -86,20 +87,16 @@ interface name. Like in
"http://[fe80::3%25eth0]/"
If you specify URL without protocol:// prefix, curl will attempt to guess what
protocol you might want. It will then default to HTTP but try other protocols
based on often-used host name prefixes. For example, for host names starting
with "ftp." curl will assume you want to speak FTP.
If you specify a URL without a protocol:// scheme, curl guesses what protocol
you want. It then defaults to HTTP but assumes others based on often-used host
name prefixes. For example, for host names starting with "ftp." curl assumes
you want FTP.
curl will do its best to use what you pass to it as a URL. It is not trying to
validate it as a syntactically correct URL by any means but is fairly liberal
with what it accepts.
curl will attempt to re-use connections for multiple file transfers, so that
getting many files from the same server will not do multiple connects /
handshakes. This improves speed. Of course this is only done on files
specified on a single command line and cannot be used between separate curl
invocations.
curl attempts to re-use connections when doing multiple file transfers, so
that getting many files from the same server do not use multiple connects /
handshakes. This improves speed. Connection re-use can only be done for URLs
specified for a single command line invocation and cannot be performed between
separate curl runs.
.SH OUTPUT
If not told otherwise, curl writes the received data to stdout. It can be
instructed to instead save that data into a local file, using the --output or