ProxyBoys

curl man page

• November 16, 2021
• 0

(HTTP) Extra header to use when getting a web page. You may specify any number of extra headers. Note that if you should add a custom header that has the same name as one of the internal ones curl would use, your externally set header will be used instead of the internal one. This allows you to make even trickier stuff than curl would normally do. You should not replace internally set headers without knowing perfectly well what you’re doing. Replacing an internal header with one without content on the right side of the colon will prevent that header from appearing.
See also the -A/–user-agent and -e/–referer options.
This option can be used multiple times to add/replace/remove multiple headers.
-i/–include
(HTTP) Include the HTTP-header in the output. The HTTP-header includes things like server-name, date of the document, HTTP-version and more…
If this option is used twice, the second will again disable header include.
–interface
Perform an operation using a specified interface. You can enter interface name, IP address or host name. An example could look like:
curl –interface eth0:1
-I/–head
(HTTP/FTP/FILE) Fetch the HTTP-header only! HTTP-servers feature the command HEAD which this uses to get nothing but the header of a document. When used on a FTP or FILE file, curl displays the file size and last modification time only.
If this option is used twice, the second will again disable header only.
-j/–junk-session-cookies
(HTTP) When curl is told to read cookies from a given file, this option will make it discard all “session cookies”. This will basicly have the same effect as if a new session is started. Typical browsers always discard session cookies when they’re closed down. 9. 7)
-k/–insecure
(SSL) This option explicitly allows curl to perform “insecure” SSL connections and transfers. Starting with curl 7. 10, all SSL connections will be attempted to be made secure by using the CA certificate bundle installed by default. This makes all connections considered “insecure” to fail unless -k/–insecure is used.
If this option is used twice, the second time will again disable it.
–key
(SSL) Private key file name. Allows you to provide your private key in this separate file.
–key-type
(SSL) Private key file type. Specify which type your –key provided private key is. DER, PEM and ENG are supported.
–krb4
(FTP) Enable kerberos4 authentication and use. The level must be entered and should be one of ‘clear’, ‘safe’, ‘confidential’ or ‘private’. Should you use a level that is not one of these, ‘private’ will instead be used.
This option requiures that the library was built with kerberos4 support. This is not very common. Use -V/–version to see if your curl supports it.
-K/–config
Specify which config file to read curl arguments from. The config file is a text file in which command line arguments can be written which then will be used as if they were written on the actual command line. Options and their parameters must be specified on the same config file line. If the parameter is to contain white spaces, the parameter must be inclosed within quotes. If the first column of a config line is a ‘#’ character, the rest of the line will be treated as a comment.
Specify the filename as ‘-‘ to make curl read the file from stdin.
Note that to be able to specify a URL in the config file, you need to specify it using the –url option, and not by simply writing the URL on its own line. So, it could look similar to this:
url = ”
–limit-rate
Specify the maximum transfer rate you want curl to use. This feature is useful if you have a limited pipe and you’d like your transfer not use your entire bandwidth.
The given speed is measured in bytes/second, unless a suffix is appended. Appending ‘k’ or ‘K’ will count the number as kilobytes, ‘m’ or M’ makes it megabytes while ‘g’ or ‘G’ makes it gigabytes. Examples: 200K, 3m and 1G.
If you are also using the -Y/–speed-limit option, that option will take precedence and might cripple the rate-limiting slightly, to help keeping the speed-limit logic working.
This option was introduced in curl 7. 10.
-l/–list-only
(FTP) When listing an FTP directory, this switch forces a name-only view. Especially useful if you want to machine-parse the contents of an FTP directory since the normal directory view doesn’t use a standard look or format.
This option causes an FTP NLST command to be sent. Some FTP servers list only files in their response to NLST; they do not include subdirectories and symbolic links.
If this option is used twice, the second will again disable list only.
-L/–location
(HTTP/HTTPS) If the server reports that the requested page has a different location (indicated with the header line Location:) this flag will let curl attempt to reattempt the get on the new place. If used together with -i/–include or -I/–head, headers from all requested pages will be shown. If authentication is used, curl will only send its credentials to the initial host, so if a redirect takes curl to a different host, it won’t intercept the user+password. See also –location-trusted on how to change this.
If this option is used twice, the second will again disable location following.
–location-trusted
(HTTP/HTTPS) Like -L/–location, but will allow sending the name + password to all hosts that the site may redirect to. This may or may not introduce a security breach if the site redirects you do a site to which you’ll send your authentication info (which is plaintext in the case of HTTP Basic authentication).
–max-filesize
Specify the maximum size (in bytes) of a file to download. If the file requested is larger than this value, the transfer will not start and curl will return with exit code 63.
NOTE: The file size is not always known prior to download, and for such files this option has no effect even if the file transfer ends up being larger than this given limit. This concerns both FTP and HTTP transfers.
-m/–max-time
Maximum time in seconds that you allow the whole operation to take. This is useful for preventing your batch jobs from hanging for hours due to slow networks or links going down. This doesn’t work fully in win32 systems. See also the –connect-timeout option.
-M/–manual
Manual. Display the huge help text.
-n/–netrc
Makes curl scan the file in the user’s home directory for login name and password. This is typically used for ftp on unix. If used with, curl will enable user authentication. See netrc(4) or ftp(1) for details on the file format. Curl will not complain if that file hasn’t the right permissions (it should not be world nor group readable). The environment variable “HOME” is used to find the home directory.
A quick and very simple example of how to setup a to allow curl to ftp to the machine with user name &zerosp;’myself’ and password ‘secret’ should look similar to:
machine login myself password secret
If this option is used twice, the second will again disable netrc usage.
–netrc-optional
Very similar to –netrc, but this option makes the usage optional and not mandatory as the –netrc does.
–negotiate
(HTTP) Enables GSS-Negotiate authentication. The GSS-Negotiate method was designed by Microsoft and is used in their web aplications. It is primarily meant as a support for Kerberos5 authentication but may be also used along with another authentication methods. For more information see IETF draft (Added in 7. 6)
This option requiures that the library was built with GSSAPI support. Use -V/–version to see if your version supports GSS-Negotiate.
-N/–no-buffer
Disables the buffering of the output stream. In normal work situations, curl will use a standard buffered output stream that will have the effect that it will output the data in chunks, not necessarily exactly when the data arrives. Using this option will disable that buffering.
If this option is used twice, the second will again switch on buffering.
–ntlm
(HTTP) Enables NTLM authentication. The NTLM authentication method was designed by Microsoft and is used by IIS web servers. It is a proprietary protocol, reversed engineered by clever people and implemented in curl based on their efforts. This kind of behavior should not be endorsed, you should encourage everyone who uses NTLM to switch to a public and documented authentication method instead. Such as Digest. 6)
If you want to enable NTLM for your proxy authentication, then use –proxy-ntlm.
This option requiures that the library was built with SSL support. Use -V/–version to see if your curl supports NTLM.
-o/–output
Write output to instead of stdout. If you are using {} or [] to fetch multiple documents, you can use ‘#’ followed by a number in the specifier. That variable will be replaced with the current string for the URL being fetched. Like in:
curl {one, two} -o “”
or use several variables like:
curl {site, host}[1-5] -o “#1_#2”
You may use this option as many times as you have number of URLs.
See also the –create-dirs option to create the local directories dynamically.
-O/–remote-name
Write output to a local file named like the remote file we get. (Only the file part of the remote file is used, the path is cut off. )
–pass (SSL) Pass phrase for the private key
–proxy-ntlm
Tells curl to use NTLM authentication when communicating with the given proxy. Use –ntlm for enabling NTLM with a remote host.
If this option is used twice, the second will again disable proxy NTLM.
-p/–proxytunnel
When an HTTP proxy is used (-x/–proxy), this option will cause non-HTTP protocols to attempt to tunnel through the proxy instead of merely using it to do HTTP-like operations. The tunnel approach is made with the HTTP proxy CONNECT request and requires that the proxy allows direct connect to the remote port number curl wants to tunnel through to.
If this option is used twice, the second will again disable proxy tunnel.
-P/–ftp-port