diff options
| author | Daniel Stenberg <daniel@haxx.se> | 2020-10-26 23:38:52 +0100 |
|---|---|---|
| committer | Daniel Stenberg <daniel@haxx.se> | 2020-10-27 23:20:03 +0100 |
| commit | 313b831ee9ef5300e829eb9e501f1d46fe7cdf5f (patch) | |
| tree | c5e315b96584f2494214e2b7df44cd997017d192 | |
| parent | 61630a155e1a81899ae99b1a5f284072606716e0 (diff) | |
| download | curl-bagder/manpage-output.tar.gz | |
curl.1: add an "OUTPUT" section at the top of the manpagebagder/manpage-output
Explain the basic concepts behind curl output.
Inspired by #6124
| -rw-r--r-- | docs/cmdline-opts/page-header | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/cmdline-opts/page-header b/docs/cmdline-opts/page-header index a51e485ba..62e97120d 100644 --- a/docs/cmdline-opts/page-header +++ b/docs/cmdline-opts/page-header @@ -99,6 +99,15 @@ 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 invokes. +.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 +--remote-name options. If curl is given multiple URLs to transfer on the +command line, it similarly needs multiple options for where to save them. + +curl does not parse or otherwise "understand" the content it gets or writes as +output. It does no encoding or decoding, unless explictly asked so with +dedicated command line options. .SH PROTOCOLS curl supports numerous protocols, or put in URL terms: schemes. Your particular build may not support them all. |