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.
Starting in curl 8.13.0, curl can be told to download URLs provided in a text file, one URL per line. It is done with --url @filename: so instead of a URL, you specify a filename prefixed with the @ symbol. It can be told to load the list of URLs from stdin by providing an argument like @-.
When downloading URLs given in a file, it implies using --remote-name for each provided URL. The URLs are full, there is no globbing applied or done on these. Features such as --skip-existing work fine in combination with this.
Lines in the URL file that start with # are treated as comments and are skipped.
This server refuses filter tree:0 (learned earlier in this isolate), so ply asked for blob:none directly. That brings every tree under the commit, not just one.
Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.