12345678910111213141516171819202122232425262728293031323334353637383940414243 |
- c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
- SPDX-License-Identifier: curl
- Long: upload-file
- Short: T
- Arg: <file>
- Help: Transfer local FILE to destination
- Category: important upload
- Example: -T file $URL
- Example: -T "img[1-1000].png" ftp://ftp.example.com/
- Example: --upload-file "{file1,file2}" $URL
- Added: 4.0
- See-also: get head request data
- Multi: append
- ---
- This transfers the specified local file to the remote URL.
- If there is no file part in the specified URL, curl appends the local file
- name to the end of the URL before the operation starts. You must use a
- trailing slash (/) on the last directory to prove to curl that there is no
- file name or curl thinks that your last directory name is the remote file name
- to use.
- When putting the local file name at the end of the URL, curl ignores what is
- on the left side of any slash (/) or backslash (\\) used in the file name and
- only appends what is on the right side of the rightmost such character.
- Use the file name "-" (a single dash) to use stdin instead of a given file.
- Alternately, the file name "." (a single period) may be specified instead of
- "-" to use stdin in non-blocking mode to allow reading server output while
- stdin is being uploaded.
- If this option is used with a HTTP(S) URL, the PUT method is used.
- You can specify one --upload-file for each URL on the command line. Each
- --upload-file + URL pair specifies what to upload and to where. curl also
- supports "globbing" of the --upload-file argument, meaning that you can upload
- multiple files to a single URL by using the same URL globbing style supported
- in the URL.
- When uploading to an SMTP server: the uploaded data is assumed to be RFC 5322
- formatted. It has to feature the necessary set of headers and mail body
- formatted correctly by the user as curl does not transcode nor encode it
- further in any way.
|