curl.1: mention quoting in the URL section

and separate the example URLs with newlines
This commit is contained in:
Daniel Stenberg 2014-10-01 08:29:43 +02:00
parent ee0958cb4d
commit 69ce8a72f5

@ -53,7 +53,9 @@ braces as in:
or you can get sequences of alphanumeric series by using [] as in: or you can get sequences of alphanumeric series by using [] as in:
ftp://ftp.numericals.com/file[1-100].txt ftp://ftp.numericals.com/file[1-100].txt
ftp://ftp.numericals.com/file[001-100].txt (with leading zeros) ftp://ftp.numericals.com/file[001-100].txt (with leading zeros)
ftp://ftp.letters.com/file[a-z].txt ftp://ftp.letters.com/file[a-z].txt
Nested sequences are not supported, but you can use several ones next to each Nested sequences are not supported, but you can use several ones next to each
@ -68,8 +70,14 @@ You can specify a step counter for the ranges to get every Nth number or
letter: letter:
http://www.numericals.com/file[1-100:10].txt http://www.numericals.com/file[1-100:10].txt
http://www.letters.com/file[a-z:2].txt http://www.letters.com/file[a-z:2].txt
When using [] or {} sequences when invoked from a command line prompt, you
probably have to put the full URL within double quotes to avoid the shell from
interfering with it. This also goes for other characters treated special, like
for example '&', '?' and '*'.
If you specify URL without protocol:// prefix, curl will attempt to guess what 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 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 based on often-used host name prefixes. For example, for host names starting