35 lines
1.1 KiB
Markdown
35 lines
1.1 KiB
Markdown
---
|
|
c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
|
|
SPDX-License-Identifier: curl
|
|
Long: url
|
|
Arg: <url>
|
|
Help: URL to work with
|
|
Category: curl
|
|
Added: 7.5
|
|
Multi: append
|
|
See-also:
|
|
- next
|
|
- config
|
|
Example:
|
|
- --url $URL
|
|
---
|
|
|
|
# `--url`
|
|
|
|
Specify a URL to fetch or send data to.
|
|
|
|
If the given URL is missing a scheme (such as `http://` or `ftp://` etc) curl
|
|
guesses which scheme to use based on the hostname. If the outermost subdomain
|
|
name matches DICT, FTP, IMAP, LDAP, POP3 or SMTP case insensitively, then that
|
|
protocol is used, otherwise it assumes HTTP. Scheme guessing can be avoided by
|
|
providing a full URL including the scheme, or disabled by setting a default
|
|
protocol, see --proto-default for details.
|
|
|
|
To control where the contents of a retrieved URL is written instead of the
|
|
default stdout, use the --output or the --remote-name options. When retrieving
|
|
multiple URLs in a single invoke, each provided URL needs its own dedicated
|
|
destination option unless --remote-name-all is used.
|
|
|
|
On Windows, `file://` accesses can be converted to network accesses by the
|
|
operating system.
|