Linux curl with cookies

Как использовать cURL для отправки кукиз

Отправить cookie в cURL можно опцией —cookie:

У опции —cookie есть короткий вариант -b. С этими опциями можно указать как файл, содержащий кукиз, так и строку с паролй ИМЯ=ЗНАЧЕНИЕ. Если аргументом является строка с символом ‘=‘, то он передаётся как есть. В противном случае строка трактуется как имя файла из которого нужно прочитать кукиз.

Сразу несколько кукиз можно передать разделив их точкой с запятой, например:

Если вы хотите сохранить кукиз, то для этого используется опция -c (длинное написание —cookie-jar). Следующий пример запишет полученные от хоста кукиз в файл cookiefile:

А следующий пример прочитает кукиз из файла cookiefile и отправит их хосту:

Смотрите также примеры в статье «Парсинг сайтов: азы, продвинутые техники, сложные случаи» раздел «cURL и аутентификация в веб-формах (передача данных методом GET и POST)».

Допустимо использовать опции для записи и чтения кукиз одновременно в один и тот же файл, как это делают веб-браузеры:

Если нужно написать файл кукиз вручную, то помните, что в документации curl сказано, что используется старый формат файлов кукиз Netscape, который отличается от формата, используемого веб-браузерами. Если вам нужно создать файл кукиз для curl вручную, то это сообщение должно помочь вам.

Файл должен быть записан примерно так:

то есть содержать 7 разделённых табом поолей: домен, tailmatch, путь, безопасность, истекают, имя, значение.

Источник

Утилита командной строки CURL

CURL — утилита командной строки для Linux или Windows, поддерживает работу с протоколами: FTP, FTPS, HTTP, HTTPS, TFTP, SCP, SFTP, Telnet, DICT, LDAP, POP3, IMAP и SMTP. Она отлично подходит для имитации действий пользователя на страницах сайтов и других операций с URL адресами. Поддержка CURL добавлена в множество различных языков программирования и платформ.

Для начала скачаем саму утилиту, для этого переходим на официальный сайт утилиты, в раздел Download. После скачивания архива для своей платформы (у меня это Windows 64 bit), распаковываем архив. Чтобы иметь возможность работать с HTTPS и FTPS, устанавливаем сертификат безопасности url-ca-bundle.crt , который находится в папке curl/bin .

Запускаем командную строку, переходим в директорию curl/bin и пытаемся скачать главную страницу Google:

Опция -X позволяет задать тип HTTP-запроса вместо используемого по умолчанию GET. Дополнительные запросы могут быть POST, PUT и DELETE или связанные с WebDAV — PROPFIND, COPY, MOVE и т.п.

Следовать за редиректами

Сервер Google сообщил нам, что страница google.com перемещена (301 Moved Permanently), и теперь надо запрашивать страницу www.google.com . С помощью опции -L укажем CURL следовать редиректам:

Сохранить вывод в файл

Чтобы сохранить вывод в файл, надо использовать опции -o или -O :

• -o ( o нижнего регистра) — результат будет сохранён в файле, заданном в командной строке;
• -O ( O верхнего регистра) — имя файла будет взято из URL и будет использовано для сохранения полученных данных.

Сохраняем страницу Google в файл google.html :

Сохраняем документ gettext.html в файл gettext.html :

Загрузить файл, только если он изменён

Опция -z позволяет получить файлы, только если они были изменены после определённого времени. Это будет работать и для FTP и для HTTP. Например, файл archive.zip будет получен, если он изменялся после 20 августа 2018 года:

Команда ниже загрузит файл archive.zip , если он изменялся до 20 августа 2018 года:

Прохождение аутентификации HTTP

Опция -u позволяет указать данные пользователя (имя и пароль) для прохождения базовой аутентификаци (Basic HTTP Authentication):

Получение и отправка cookie

Cookie используются сайтами для хранения некой информации на стороне пользователя. Сервер сохраняет cookie на стороне клиента (т.е. в браузере), отправляя заголовки:

А браузер, в свою очередь, отправляет полученные cookie обратно на сервер при каждом запросе. Разумеется, тоже в заголовках:

Передать cookie на сервер, как будто они были ранее получены от сервера:

Чтобы сохранить полученные сookie в файл:

Затем можно отправить сохраненные в файле cookie обратно:

Файл cookie.txt имеет вид:

Получение и отправка заголовков

По умолчанию, заголовки ответа сервера не показываются. Но это можно исправить:

Если содержимое страницы не нужно, а интересны только заголовки (будет отправлен HEAD запрос):

Посмотреть, какие заголовки отправляет CURL при запросе, можно с помощью опции -v , которая выводит более подробную информацию:

• Строка, начинающаяся с > означает заголовок, отправленный серверу
• Строка, начинающаяся с означает заголовок, полученный от сервера
• Строка, начинающаяся с * означает дополнительные данные от CURL

А вот так можно отправить свой заголовок:

Отправка данных методом POST

Команда ниже отправляет POST запрос на сервер аналогично тому, как пользователь, заполнив HTML форму, нажал бы кнопку «Отправить». Данные будут отправлены в формате application/x-www-form-urlencoded .

Параметр —data аналогичен —data-ascii , для отправки двоичных данных необходимо использовать параметр —data-binary . Для URL-кодирования полей формы нужно использовать —data-urlencode .

Если значение опции —data начинается с @ , то после него должно быть имя файла с данными (или дефис — тогда будут использованы данные из стандартного ввода). Пример получения данных из файла для отправки POST-запроса:

Содержимое файла data.txt :

Массив $_POST , который будет содержать данные этого запроса:

Пример URL-кодирования данных из файла перед отправкой POST-запроса:

Содержимое файла username.txt :

Массив $_POST , который будет содержать данные этого запроса:

Загрузка файлов методом POST

Для HTTP запроса типа POST существует два варианта передачи полей из HTML форм, а именно, используя алгоритм application/x-www-form-urlencoded и multipart/form-data . Алгоритм первого типа создавался давным-давно, когда в языке HTML еще не предусматривали возможность передачи файлов через HTML формы.

Со временем возникла необходимость через формы отсылать еще и файлы. Тогда консорциум W3C взялся за доработку формата POST запроса, в результате чего появился документ RFC 1867. Форма, которая позволяет пользователю загрузить файл, используя алгоритм multipart/form-data , выглядит примерно так:

Чтобы отправить на сервер данные такой формы:

Скрипт upload.php , который принимает данные формы:

Работа по протоколу FTP

Скачать файл с FTP-сервера:

Если заданный FTP путь является директорией, то по умолчанию будет выведен список файлов в ней:

Источник

How do I send Cookies using Curl?

Compare Request Timings

What is Curl?

The Curl is a command-line tool available for Linux, Windows, and macOS and a cross-platform library (libcurl) that can be used with almost any application written in nearly any programming language. Curl uses URL syntax to transfer data to and from servers. With Curl, you can upload or download data, submit web forms, and make API requests using over 25 protocols, including HTTP, HTTPS, FTP, and SFTP.

What is Cookie?

Cookies are small blocks of data sent from a website and stored by a web browser on a user’s computer. Cookies are placed on the device used to access the website (computer, mobile phone, etc.). Several cookies may be placed on the same computer during a session. Browsers send cookies back to the server with each subsequent request, allowing the server to determine if the request came from the same browser or not.

Cookies enable web servers to store state information on a user’s device or track a user’s online activity. The data stored in cookies are created by the server when it connects to the server. This data is tagged with an identifier that is unique to user and user’s computer. Cookies are primarily used for user session management, user tracking, and personalization.

How set Cookie with Curl?

The general form of the Curl command for sending a Cookies request is as follows:

What is cookie-jar?

The -c (or —cookie-jar) command-line option specifies the filename where Curl should write all cookies after the operation completes. Curl will report to the specified file all the cookies from its in-memory cookie store at the end of the process. If there are no cookies, Curl will not create the specified file. If you include a dash «-» for a filename, Curl will write cookies to standard output.

How to set cookies for Curl?

You can use the -b (or —cookie) command-line switch to pass cookies to Curl.

How to use Сookies with Libcurl?

Libcurl is a free client library that can add the same capabilities to your application as the Curl command-line tool. Libcurl is portable, thread-safe, IPv6 compatible, and can be used on many platforms, including Windows, Linux, and has bindings for many popular programming languages, including C++, JavaScript, PHP, Python, and others. Libcurl offers several ways to enable and interact with cookies in your application:

Options	Action
CURLOPT_COOKIE	Provide a cookie header to be sent to the server.
CURLOPT_COOKIEFILE	Read cookies from the given cookie jar file.
CURLOPT_COOKIEJAR	Save cookies to the specified cookie jar file.
CURLOPT_COOKIELIST	Provide details of one cookie.
CURLINFO_COOKIELIST	Extract cookie information from cookie storage.

See also

Generate Code Snippets for Curl Send Cookies Example

Convert your Curl Send Cookies request to the PHP, JavaScript/AJAX, Curl/Bash, Python, Java, C#/.NET code snippets using the ReqBin code generator.

Источник

Linux curl command

The curl command transfers data to or from a network server, using one of the supported protocols (HTTP, HTTPS, FTP, FTPS, SCP, SFTP, TFTP, DICT, TELNET, LDAP or FILE). It is designed to work without user interaction, so it is ideal for use in a shell script.

The software offers proxy support, user authentication, FTP uploading, HTTP posting, SSL connections, cookies, file transfer resume, metalink, and other features.

Syntax

Options

-a, —append

(FTP/SFTP) When used in an FTP upload, this will tell curl to append to the target file instead of overwriting it. If the file doesn’t exist, it is created.

Note that this option is ignored by some SSH servers, including OpenSSH. -A, —user-agent

(HTTP) Specify the User-Agent string to send to the HTTP server. Some CGI fail if the agent string is not set to «Mozilla/4.0«. To encode blanks in the string, surround the string with single quote marks.

This value can also be set with the -H/—header option.

If this option is set more than once, the last one will be the one that’s used. —anyauth (HTTP) Tells curl to figure out authentication method by itself, and use the most secure method the remote site claims it supports. This is done by first making a request and checking the response-headers, thus possibly inducing a network round-trip. This is used instead of setting a specific authentication method, which you can do with —basic, —digest, —ntlm, and —negotiate.

Note that using —anyauth is not recommended if you do uploads from stdin since it may require data to be sent twice and then the client must be able to rewind. If the need should arise when uploading from stdin, the upload operation fails. -b, —cookie (HTTP) Pass the data to the HTTP server as a cookie. It is expected to be the data previously received from the server in a «Set-Cookie:» line. The data should be in the format «NAME1=VALUE1; NAME2=VALUE2«.

If no ‘=‘ (equals) character is used in the line, it is treated as a file name to use to read previously stored cookie lines from, which should be used in this session if they match. Using this method also activates the «cookie parser» which makes curl record incoming cookies too, which may be handy if you’re using this in combination with the —location option. The file format of the file to read cookies from should be plain HTTP headers or the Netscape/Mozilla cookie file format.

NOTE: the file specified with -b/—cookie is only used as input. No cookies will be stored in the file. To store cookies, use the -c/—cookie-jar option, or you can save the HTTP headers to a file using -D/—dump-header.

If this option is set more than once, the last occurrence will be the option that’s used. -B, —use-ascii (FTP/LDAP) Enable ASCII transfer. For FTP, this can also be enforced using an URL that ends with «;Type=A«. This option causes data sent to stdout to be in text mode for win32 systems.

If this option is used twice, the second one disables ASCII usage. —basic (HTTP) Tells curl to use HTTP Basic authentication. This is the default and this option is usually pointless, unless you use it to override a previously set option that sets a different authentication method (such as —ntlm, —digest and —negotiate). —ciphers

(SSL) Specifies which ciphers to use in the connection. The ciphers listed must be valid. You can read up on SSL cipher list details at openssl.org.

NSS ciphers are done differently than OpenSSL and GnuTLS. The full list of NSS ciphers is in the NSSCipherSuite entry at this URL: https://pagure.io/mod_nss#Directives.

If this option is used several times, the last one overrides the others. —compressed (HTTP) Request a compressed response using one of the algorithms curl supports, and return the uncompressed document. If this option is used and the server sends an unsupported encoding, Curl will report an error. —connect-timeout Maximum time in seconds that the connection to the server may take. This only limits the connection phase; once curl has connected this option no longer applies. Since 7.32.0, this option accepts decimal values, but the actual timeout decreases in accuracy as the specified timeout increases in decimal precision. See also the -m/—max-time option.

If this option is used several times, the last one will be used. -c, —cookie-jar (HTTP) Specify what file you want curl to write all cookies after a completed operation. Curl writes all cookies previously read from a specified file and all cookies received from remote server(s). If no cookies are known, no file will be written. The file will be written using the Netscape cookie file format. If you set the file name to a single dash («—«), the cookies will be written to stdout.

This command line option activates the cookie engine that makes curl record and use cookies. Another way to activate it is to use the -b/—cookie option.

NOTE: If the cookie jar can’t be created or written to, the whole curl operation won’t fail or even report an error. If -v is specified a warning is displayed, but that is the only visible feedback you get about this possibly fatal situation.

If this option is used several times, the last specified file name will be used. -C, —continue-at Continue/Resume a previous file transfer at the given offset. The given offset is the exact number of bytes that will be skipped, counted from the beginning of the source file before it is transferred to the destination. If used with uploads, the ftp server command SIZE is not used by curl.

Use «-C —» to tell curl to automatically find out where/how to resume the transfer. It then uses the given output/input files to figure that out.

If this option is used several times, the last one will be used. —create-dirs When used in conjunction with the -o option, curl creates the necessary local directory hierarchy as needed. This option creates the dirs mentioned with the -o option, nothing else. If the -o file name uses no directory or if the directories it mentions already exist, no directories are created.

To create remote directories when using FTP or SFTP, try —ftp-create-dirs. —crlf (FTP) Convert LF to CRLF in upload. Useful for MVS (OS/390). —crlfile (HTTPS/FTPS) Provide a file using PEM format with a Certificate Revocation List that may specify peer certificates that are to be considered revoked.

If this option is used several times, the last one will be used.

(Added in 7.19.7) -d, —data (HTTP) Sends the specified data in a POST request to the HTTP server, in a way that emulates as if a user has filled in an HTML form and pressed the submit button. Note that the data is sent exactly as specified with no extra processing (with all newlines cut off). The data is expected to be «url-encoded». This causes curl to pass the data to the server using the content-type application/x-www-form-urlencoded. Compare to -F/—form. If this option is used more than once on the same command line, the data pieces specified will be merged together with a separating «&» character. Thus, using ‘-d name=daniel -d skill=lousy’ would generate a POST chunk that looks like ‘name=daniel&skill=lousy’.

If you start the data with the «@» character, the rest should be a file name to read the data from, or «—» (dash) if you want curl to read the data from stdin. The contents of the file must already be url-encoded. Multiple files can also be specified. Posting data from a file named ‘foobar’ would thus be done with «—data @foo-bar«.

-d/—data is the same as —data-ascii. To post data purely binary, use the —data-binary option. To URL-encode the value of a form field you may use —data-urlencode.

If this option is used several times, the ones following the first will append data. —data-ascii (HTTP) This is an alias for the -d/—data option.

If this option is used several times, the ones following the first will append data. —data-binary (HTTP) This posts data exactly as specified with no extra processing whatsoever.

If you start the data with the character @, the rest should be a filename. Data is posted in a similar manner as —data-ascii does, except that newlines are preserved and conversions are never done.
If this option is used several times, the ones following the first will append data as described in -d, —data. —data-urlencode (HTTP) This posts data, similar to the other —data options with the exception that this performs URL-encoding. (Added in 7.18.0)

To be CGI-compliant, the part should begin with a name followed by a separator and a content specification. The part can be passed to curl using one of the following syntaxes:

This makes curl URL-encode the content and pass that on. Just be careful so that the content doesn’t contain any = or @ symbols, as that will then make the syntax match one of the other cases below!

This makes curl URL-encode the content and pass that on. The preceding = symbol is not included in the data.

This makes curl URL-encode the content part and pass that on. Note that the name part is expected to be URL-encoded already.

This makes curl load data from the given file (including any newlines), URL-encode that data and pass it on in the POST.

This makes curl load data from the given file (including any newlines), URL-encode that data and pass it on in the POST. The name part gets an equal sign appended, resulting in name=urlencoded-file-content. Note that the name is expected to be URL-encoded already. —delegation LEVEL Set LEVEL to tell the server what it is allowed to delegate with the user credentials. Used with GSS/kerberos.

Don’t allow any delegation.

Delegates if and only if the OK-AS-DELEGATE flag is set in the Kerberos service ticket, which is a matter of realm policy.

Unconditionally allow the server to delegate. —digest (HTTP) Enables HTTP Digest authentication. This is an authentication that prevents the password from being sent as clear text. Use this in combination with the normal -u/—user option to set username and password. See also —ntlm, —negotiate and —anyauth for related options.

If this option is used several times, the following occurrences make no difference. —disable-eprt (FTP) Tell curl to disable the use of the EPRT and LPRT commands when doing active FTP transfers. Curl will normally always first attempt to use EPRT, then LPRT before using PORT, but with this option, it uses PORT right away. EPRT and LPRT are extensions to the original FTP protocol, may not work on all servers but enable more functionality in a better way than the traditional PORT command.

—eprt can explicitly enable EPRT again and —no-eprt is an alias for —disable-eprt.

Disabling EPRT only changes the active behavior. If you want to switch to passive mode you need to not use -P, —ftp-port or force it with —ftp-pasv. —disable-epsv (FTP) Tell curl to disable the use of the EPSV command when doing passive FTP transfers. Curl will normally always first attempt to use EPSV before PASV, but with this option, it will not try using EPSV.

—epsv can explicitly enable EPSV again and —no-epsv is an alias for —disable-epsv.

Disabling EPSV only changes the passive behavior. If you want to switch to active mode you need to use -P, —ftp-port. -D, —dump-header Write the protocol headers to the specified file.

This option is handy to use when you want to store the headers that an HTTP site sends to you. Cookies from the headers could then be read in a second curl invoke using the -b/—cookie option. However, the -c/—cookie-jar option is a better way to store cookies.

When used on FTP, the ftp server response lines are considered being «headers» and thus are saved there.

If this option is used several times, the last one is used. -e, —referer (HTTP) Sends the «Referer Page» information to the HTTP server. This can also be set with the -H/—header. When used with -L/—location, you can append «;auto» to the —referer URL to make curl automatically set the previous URL when it follows a Location: header. The «;auto» string can be used alone, even if you don’t set an initial —referer.

If this option is used several times, the last one will be used. —engine Select the OpenSSL crypto engine to use for cipher operations. Use —engine list to print a list of build-time supported engines. Note that not all (or none) of the engines may be available at run time. —environment (RISC OS ONLY) Sets a range of environment variables, using the names the -w option supports, to easier allow extraction of useful information after having run curl. —egd-file (HTTPS) Specify the path name to the Entropy Gathering Daemon socket. The socket is used to seed the random engine for SSL connections. See also the —random-file option. -E, —cert (SSL) Tells curl to use the specified client certificate file when getting a file with HTTPS, FTPS or another SSL-based protocol. The certificate must be in PEM format. If the optional password isn’t specified, it will be queried for on the terminal. Note that this option assumes a «certificate» file that is the private key and the private certificate concatenated. See —cert and —key to specify them independently.

If curl is built against the NSS SSL library then this option can tell curl the nickname of the certificate to use in the NSS database defined by the environment variable SSL_DIR (or by default /etc/pki/nssdb). If the NSS PEM PKCS#11 module (libnsspem.so) is available then PEM files may be loaded. If you want to use a file from the current directory, please precede it with «./» prefix, to avoid confusion with a nickname. If the nickname contains «:«, it needs to be preceded by «\» so that it is not recognized as password delimiter. If the nickname contains «\«, it needs to be escaped as «\\» so that it is not recognized as an escape character.

(iOS and Mac OS X only) If curl is built against Secure Transport, then the certificate string must match the name of a certificate that’s in the system or user keychain. The private key corresponding to the certificate, and certificate chain (if any), must also be present in the keychain.

If this option is used several times, the last one will be used. —cert-type (SSL) Tells curl the type of certificate type of the provided certificate. PEM, DER and ENG are recognized types. If not specified, PEM is assumed.

If this option is used several times, the last one will be used. —cacert (SSL) Tells curl to use the specified certificate file to verify the peer. The file may contain multiple CA certificates. The certificate(s) must be in PEM format. Normally curl is built to use a default file for this, so this option is used to alter that default file.

curl recognizes the environment variable named ‘CURL_CA_BUNDLE‘ if that is set, and uses the given path as a path to a CA cert bundle. This option overrides that variable.

The Windows version of curl automatically looks for a CA certs file named ‘curl-ca-bundle.crt‘, either in the same directory as curl.exe, or in the current working directory, or in any folder along your PATH.

If curl is built against the NSS SSL library, the NSS PEM PKCS#11 module (libnsspem.so) needs to be available for this option to work properly.

If this option is used several times, the last one will be used. —capath (SSL) Tells curl to use the specified certificate directory to verify the peer. The certificates must be in PEM format, and the directory must be processed using the c_rehash utility supplied with openssl. Using —capath can allow curl to make https connections much more efficiently than using —cacert if the —cacert file contains many CA certificates.

If this option is used several times, the last one will be used. -f, —fail (HTTP) Fail silently (no output at all) on server errors. This is mostly done to better enable scripts, etc. to better deal with failed attempts. In normal cases when an HTTP server fails to deliver a document, it returns an HTML document stating so (which often also describes why). This flag prevents curl from outputting that and return error 22.

This method is not fail-safe and there are occasions where non-successful response codes will slip through, especially when authentication is involved (response codes 401 and 407). —ftp-account [data] (FTP) When an FTP server asks for «account data» after username and password was provided, this data is sent off using the ACCT command. (Added in 7.13.0)

If this option is used twice, the second overrides the previous use. —ftp-create-dirs (FTP/SFTP) When an FTP URL/operation uses a path that doesn’t currently exist on the server, the standard behavior of curl is to fail. Using this option, curl will instead attempt to create missing directories. —ftp-method [method] (FTP) Control what method curl should use to reach a file on an FTP(S) server. The method argument should be one of the following alternatives:

curl does a single CWD operation for each path part in the given URL. For deep hierarchies this means a lot of commands. This is the default but the slowest behavior.

curl does no CWD at all. curl will do SIZE, RETR, STOR, etc. and give a full path to the server for all these commands. This is the fastest behavior.

curl does one CWD with the full target directory and then operates on the file «normally» (like in the multicwd case). This is somewhat more standards-compliant than ‘nocwd‘ but without the full penalty of ‘multicwd‘. —ftp-pasv (FTP) Use PASV when transferring. PASV is the internal default behavior, but using this option can override a previous —ftp-port option. (Added in 7.11.0)

If this option is used several times, the following occurrences make no difference. Undoing an enforced passive really isn’t doable but you must then instead enforce the correct -P, —ftp-port again.

Passive mode means that curl will try the EPSV command first and then PASV, unless —disable-epsv is used. —ftp-alternative-to-user (FTP) If authenticating with the USER and PASS commands fail, send this command. When connecting to Tumbleweed’s Secure Transport server over FTPS using a client certificate, using «SITE AUTH» will tell the server to retrieve the username from the certificate. (Added in 7.15.5) —ftp-skip-pasv-ip (FTP) Tell curl to not use the IP address the server suggests in its response to curl‘s PASV command when curl connects the data connection. Instead, curl will re-use the same IP address it already uses for the control connection. (Added in 7.14.2)

This option has no effect if PORT, EPRT or EPSV is used instead of PASV. —ftp-pret (FTP) Tell curl to send a PRET command before PASV (and EPSV). Certain FTP servers, mainly drftpd, require this non-standard command for directory listings and up and downloads in PASV mode. (Added in 7.20.x) —ftp-ssl (FTP) Try to use SSL/TLS for the FTP connection. Reverts to a non-secure connection if the server doesn’t support SSL/TLS. (Added in 7.11.0)

If this option is used twice, the second will again disable this. —ftp-ssl-ccc (FTP) Use CCC (Clear Command Channel) Shuts down the SSL/TLS layer after authenticating. The rest of the control channel communication will be unencrypted. This allows NAT routers to follow the FTP transaction. The default mode is passive. See —ftp-ssl-ccc-mode for other modes. (Added in 7.16.1) —ftp-ssl-ccc-mode [active/passive] (FTP) Use CCC (Clear Command Channel) Sets the CCC mode. The passive mode will not initiate the shutdown, but instead wait for the server to do it, and will not reply to the shutdown from the server. The active mode initiates the shutdown and waits for a reply from the server. (Added in 7.16.2) —ftp-ssl-control (FTP) Require SSL/TLS for the FTP login, clear for transfer. Allows secure authentication, but non-encrypted data transfers for efficiency. Fails the transfer if the server doesn’t support SSL/TLS. (Added in 7.16.0) —ftp-ssl-reqd (FTP) Require SSL/TLS for the FTP connection. Terminates the connection if the server doesn’t support SSL/TLS. (Added in 7.15.5)

If this option is used twice, the second will again disable this. -F, —form (HTTP) This lets curl emulate a filled-in form where a user has pressed the submit button. This causes curl to POST data using the Content-Type multipart/form-data according to RFC1867. This enables uploading of binary files etc. To force the ‘content’ part to be a file, prefix the file name with an «@» character. To get the content part of a file, prefix the file name with the letter « (HTTP) Similar to —form except that the value string for the named parameter is used literally. Leading ‘@‘ and ‘ (HTTP) Extra header to use when getting a web page. You may specify any number of extra headers. Note that if you add a custom header with 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. Remove an internal header by giving a replacement without content on the right side of the colon, as in: -H «Host:». If you send the custom header with no-value then its header must be terminated with a semicolon, such as -H «X-Custom-Header;» to send «X-Custom-Header:«.

curl makes sure that each header you add/replace get sent with the proper end of line marker, therefore don’t add that as a part of the header content: do not add newlines or carriage returns they only mess things up for you.

See also the -A/—user-agent and -e/—referer options.

This option can be used multiple times to add/replace/remove multiple headers. —hostpubmd5 (SCP/SFTP) Pass a string containing 32 hexadecimal digits. The string should be the 128 bit MD5 checksum of the remote host’s public key, curl will refuse the connection with the host unless the md5sums match. (Added in 7.17.1) —ignore-content-length (HTTP) Ignore the Content-Length header. This is particularly useful for servers running Apache 1.x, which will report incorrect Content-Length for files larger than 2 gigabytes. -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. —interface Perform an operation using a specified interface. You can enter interface name, IP address or hostname. An example could look like:

curl —interface eth0:1 http://www.netscape.com/

If this option is used several times, the last one will be used. -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 an FTP or FILE file, curl displays the file size and last modification time only. -j, —junk-session-cookies (HTTP) When curl is told to read cookies from a file, this option makes it discard all «session cookies.» This option has the same effect as if a new session is started. Typical browsers always discard session cookies when they’re closed down. -J, —remote-header-name (HTTP) This option tells the -O, —remote-name option to use the server-specified Content-Disposition filename instead of extracting a filename from the URL. -k, —insecure (SSL) This option explicitly allows curl to perform «insecure» SSL connections and transfers. All SSL connections are attempted to be made secure using the CA certificate bundle installed by default. All connections considered «insecure» fail unless -k/—insecure is used.

See this online resource for more information: https://curl.haxx.se/docs/sslcerts.html. —key (SSL/SSH) Private key file name. Allows you to provide your private key in this separate file.

If this option is used several times, the last one will be used. —key-type (SSL) Private key file type. Specify which type your —key provided private key is. DER, PEM, and ENG are supported. If not specified, PEM is assumed.

If this option is used several times, the last one is used. —krb (FTP) Enable Kerberos 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’ instead is used.

This option requires a library built with kerberos4 or GSSAPI (GSS-Negotiate) support. This is not very common. Use -V, —version to see if your curl supports it.

If this option is used several times, the last one is used. -K, —config Specify which config file to read the curl arguments. The config file is a text file where command line arguments can be written, which then are 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 enclosed within quotes. If the first column of a config line is a ‘#‘ character, the rest of the line is treated as a comment. Only write one option per physical line in the config file.

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 writing the URL on its own line. So, it could look similar to this:

Long option names can optionally be given in the config file without the initial double dashes.

When curl is invoked, it always (unless -q is used) checks for a default config file and uses it if found. The default config file is checked for in the following places in this order:

1) curl tries to find the «home dir»: It first checks for the CURL_HOME and then the HOME environment variables. Failing that, it uses getpwuid() on unix-like systems (which returns the home dir given the current user in your system). On Windows, it then checks for the APPDATA variable, or as a last resort the ‘%USER-PROFILE%\Application Data‘.

2) On Windows, if there is no _curlrc file in the home dir, it checks for one in the same dir the executable curl is placed. On unix-like systems, it will try to load .curlrc from the determined home dir.

This option can be used multiple times to load multiple config files. —keepalive-time This option sets the time a connection needs to remain idle before sending keepalive probes and the time between individual keepalive probes. It is currently effective on operating systems offering the TCP_KEEPIDLE and TCP_KEEPINTVL socket options (meaning Linux, recent AIX, HP-UX, and more). This option has no effect if —no-keepalive is used. (Added in 7.18.0)

If this option is used several times, the last one will be used. If unspecified, the option defaults to 60 seconds. —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.

The given rate is the average speed counted during the entire transfer. It means that curl might use higher transfer speeds in short bursts, but over time it uses no more than the given rate.

If you are also using the -Y/—speed-limit option, that option takes precedence and might cripple the rate-limiting slightly, to help keep the speed-limit logic working.

If this option is used several times, the last one will be used. -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. —local-port [—num] Set a preferred number or range of local port numbers to use for the connection(s). Note that port numbers by nature are a scarce resource that will be busy at times so setting this range to something too narrow might cause unnecessary connection setup failures. (Added in 7.15.2) -L, —location (HTTP/HTTPS) If the server reports that the requested page has moved to a different location (indicated with a Location: header and a 3XX response code) this option makes curl redo the request on the new place. If used together with -i/—include or -I/—head, headers from all requested pages are shown. When authentication is used, curl only sends its credentials to the initial host. If a redirect takes curl to a different host, it won’t be able to intercept the user+password. See also —location-trusted on how to change this. You can limit the amount of redirects to follow using the —max-redirs option.

When curl follows a redirect and the request is not a plain GET (for example POST or PUT), it does the following request with a GET if the HTTP response was 301, 302, or 303. If the response code was any other 3xx code, curl re-sends the following request using the same unmodified method. —libcurl Append this option to any ordinary curl command line, and you receive as output C source code that uses libcurl, written to the file that does the equivalent of what your command-line operation does! It should be noted that this option is extremely awesome.

If this option is used several times, the last given file name is used. (Added in 7.16.1) —location-trusted (HTTP/HTTPS) Similar to -L/—location, but allows 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 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 doesn’t start and curl returns with exit code 63.

NOTE: The file size is not always known before 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 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. See also the —connect-timeout option.

If this option is used several times, the last one will be used. —mail-auth

(SMTP) Specify a single address. This will be used to specify the authentication address (identity) of a submitted message that is being relayed to another server.

(Added in 7.25.0) —mail-from

(SMTP) Specify a single address that the given mail should get sent from.

(Added in 7.20.0) —mail-rcpt

(SMTP) Specify a single address that the given mail should get sent to. This option can be used multiple times to specify many recipients.

(Added in 7.20.0) —metalink This option can tell curl to parse and process a given URI as Metalink file (both version 3 and 4 (RFC 5854) are supported) and make use of the mirrors listed within for failover if there are errors (such as the file or server not being available). It also verifies the hash of the file after the download completes. The Metalink file itself is downloaded and processed in memory and not stored in the local file system.

Example to use a remote Metalink file:

curl —metalink http://www.example.com/example.metalink

To use a Metalink file in the local file system, use FILE protocol (file://):

curl —metalink file://example.metalink

Please note that if FILE protocol is disabled, there is no way to use a local Metalink file at the time of this writing. Also, note that if —metalink and —include are used together, —include will be ignored. This is because including headers in the response will break Metalink parser and if the headers are included in the file described in Metalink file, hash check fails.

(Added in 7.27.0, if built against the libmetalink library.) -n, —netrc Makes curl scan the .netrc file in the user’s home directory for login name and password. This is used for ftp on unix. If used with http, curl enables user authentication. See netrc(4) or ftp documentation 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 set up a .netrc to allow curl to ftp to the machine host.domain.com with username ‘myself’ and password ‘secret’ should look similar to:

machine host.domain.com login myself password secret

If this option is used twice, the second will again disable netrc usage. —negotiate (HTTP) Enables GSS-Negotiate authentication. The GSS-Negotiate method was designed by Microsoft and is used in their web applications. It is primarily meant as a support for Kerberos5 authentication but may be also used with another authentication methods.

This option requires that the curl library was built with GSSAPI support. This is not very common. Use -V/—version to see if your version supports GSS-Negotiate.

When using this option, you must also provide a fake -u/—user option to activate the authentication code properly. Sending a ‘-u :‘ is enough as the username and password from the -u option aren’t actually used.

If this option is used several times, the following occurrences make no difference. —no-keepalive Disables the use of keepalive messages on the TCP connection, as by default curl enables them.

Note that this is the negated option name documented. You can thus use —keepalive to enforce keepalive. —no-sessionid (SSL) Disable curl‘s use of SSL session-ID caching. By default, all transfers are done using the cache. Note that while nothing should ever get hurt by attempting to reuse SSL session-IDs, there seem to be broken SSL implementations in the wild that may require you to disable this for you to succeed. (Added in 7.16.0)

Note that this is the negated option name documented. You can thus use —sessionid to enforce session-ID caching. —noproxy Comma-separated list of hosts which do not use a proxy, if one is specified. The only wildcard is a single * character, which matches all hosts, and effectively disables the proxy. Each name in this list is matched as either a domain which contains the hostname, or the hostname itself. For example, local.com would match local.com, local.com:80, and www.local.com, but not www.notlocal.com. (Added in 7.19.4). -N, —no-buffer Disables the buffering of the output stream. In normal work situations, curl uses a standard buffered output stream with the effect of outputting the data in chunks, not necessarily exactly when the data arrives. Using this option disables that buffering.

Note that this is the negated option name documented. You can thus use —buffer to enforce the buffering. —netrc-file This option is similar to —netrc, except you provide the path (absolute or relative) to the netrc file that curl should use. You can only specify one netrc file per invocation. If several —netrc-file options are provided, only the last one will be used. (Added in 7.21.5)

This option overrides any use of —netrc as they are mutually exclusive. It also abides by —netrc-optional if specified. —netrc-optional Very similar to —netrc, but this option makes the .netrc usage optional and not mandatory as the —netrc option does. —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, reverse-engineered by clever people and implemented in curl based on their efforts. This kind of behavior should not be endorsed, encourage everyone who uses NTLM to switch to a public and documented authentication method instead, such as Digest.

If you want to enable NTLM for your proxy authentication, then use —proxy-ntlm.

This option requires a library built with SSL support. Use -V, —version to see if your curl supports NTLM.

If this option is used several times, only the first one is used. -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:

or use several variables like:

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. Specifying the output as ‘—‘ (a single dash) will force the output to be done to stdout. -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.)

The remote file name to use for saving is extracted from the given URL, nothing else.

Consequentially, the file will be saved in the current working directory. If you want the file saved in a different directory, make sure you change current working directory before you invoke curl with the -O, —remote-name flag!

You may use this option as many times as you have number of URLs. —pass

(SSL/SSH) Pass phrase for the private key.

If this option is used several times, the last one will be used. —post301 (HTTP) Tells curl to respect RFC 2616/10.3.2 and not convert POST requests into GET requests when following a 301 redirection. The non-RFC behaviour is ubiquitous in web browsers, so curl does the conversion by default to maintain consistency. However, a server may require a POST to remain a POST after such a redirection. This option is meaningful only when using -L, —location (Added in 7.17.1) —post302 (HTTP) Tells curl to respect RFC 2616/10.3.2 and not convert POST requests into GET requests when following a 302 redirection. The non-RFC behaviour is ubiquitous in web browsers, so curl does the conversion by default to maintain consistency. However, a server may require a POST to remain a POST after such a redirection. This option is meaningful only when using -L, —location (Added in 7.19.1) —post303 (HTTP) Tells curl to respect RFC 2616/10.3.2 and not convert POST requests into GET requests when following a 303 redirection. The non-RFC behaviour is ubiquitous in web browsers, so curl does the conversion by default to maintain consistency. However, a server may require a POST to remain a POST after such a redirection. This option is meaningful only when using -L, —location (Added in 7.26.0) —proto

Tells curl to use the listed protocols for its initial retrieval. Protocols are evaluated left to right, are comma separated, and are each a protocol name or ‘all‘, optionally prefixed by zero or more modifiers. Available modifiers are:

Permit this protocol in addition to protocols already permitted (this is the default if no modifier is used).

Deny this protocol, removing it from the list of protocols already permitted.

Permit only this protocol (ignoring the list already permitted), though subject to later modification by subsequent entries in the comma separated list.

—proto -ftps uses the default protocols, but disables ftps

—proto -all,https,+http only enables http and https

—proto =http,https also only enables http and https

Unknown protocols produce a warning. This allows scripts to safely rely on being able to disable potentially dangerous protocols, without relying upon support for that protocol being built into curl to avoid an error.

This option can be used multiple times, which is the same as concatenating the protocols into one instance of the option. (Added in 7.20.2) —proto-redir

Tells curl to use the listed protocols after a redirect. See —proto for how protocols are represented. (Added in 7.20.2) —proxy-anyauth Tells curl to pick a suitable authentication method when communicating with the given proxy. This causes an extra request/response round-trip. (Added in 7.13.2) —proxy-basic Tells curl to use HTTP Basic authentication when communicating with the given proxy. Use —basic for enabling HTTP Basic with a remote host. Basic is the default authentication method curl uses with proxies. —proxy-digest Tells curl to use HTTP Digest authentication when communicating with the given proxy. Use —digest for enabling HTTP Digest with a remote host. —proxy-ntlm Tells curl to use HTTP NTLM authentication when communicating with the given proxy. Use —ntlm for enabling NTLM with a remote host. —proxy1.0

Use the specified HTTP 1.0 proxy. If the port number is not specified, it is assumed at port 1080.

The only difference between this and the HTTP proxy option (-x, —proxy), is that attempts to use CONNECT through the proxy specifying an HTTP 1.0 protocol instead of the default HTTP 1.1. —pubkey (SSH) Public key file name. Allows you to provide your public key in this separate file.

If this option is used several times, the last one is used. -p, —proxytunnel When an HTTP proxy is used (-x, —proxy), this option causes 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. -P, —ftp-port

(FTP) Reverses the default initiator/listener roles when connecting with FTP. This switch makes curl use active mode. In practice, curl then tells the server to connect back to the client’s specified address and port, while passive mode asks the server to set up an IP address and port for it to connect to. should be one of:

i.e «eth0» to specify which interface’s IP address you want to use (Unix only)

i.e «192.168.10.1» to specify the exact IP address

i.e «my.host.domain» to specify the machine

make curl pick the same IP address that is already used for the control connection.

If this option is used several times, the last one is used. Disable the use of PORT with —ftp-pasv. Disable the attempt to use the EPRT command instead of PORT using —disable-eprt. EPRT is really PORT++.

Starting in 7.19.5, you can append «:[start]-[end]» to the right of the address, to tell curl what TCP port range to use. That means you specify a port range, from a lower to a higher number. A single number works as well, but do note that it increases the risk of failure since the port may not be available. -q If used as the first parameter on the command line, the curlrc config file is not read and used. See the -K, —config for details on the default config file search path. -Q, —quote (FTP/SFTP) Send an arbitrary command to the remote FTP or SFTP server. Quote commands are sent BEFORE the transfer is taking place (after the initial PWD command to be exact). To make commands take place after a successful transfer, prefix them with a dash ‘—‘. To make commands get sent after libcurl has changed working directory, before the transfer command(s), prefix the command with ‘+‘ (this is only supported for FTP). You may specify any amount of commands. If the server returns failure for one of the commands, the entire operation will be aborted. You must send syntactically correct FTP commands as RFC959 defines to FTP servers, or one of the commands listed below to SFTP servers.

This option can be used multiple times. When speaking to an FTP server, prefix the command with an asterisk (*) to make curl continue even if the command fails as by default curl stops at first failure.

SFTP is a binary protocol. Unlike for FTP, curl interprets SFTP quote commands itself before sending them to the server. File names may be quoted shell-style to embed spaces or special characters. Following is the list of all supported SFTP quote commands:

chgrp group file

The chgrp command sets the group ID of the file named by the file operand to the group ID specified by the group operand. The group operand is a decimal integer group ID.

chmod mode file

The chmod command modifies the file mode bits of the specified file. The mode operand is an octal integer mode number.

chown user file

The chown command sets the owner of the file named by the file operand to the user ID specified by the user operand. The user operand is a decimal integer user ID.

ln source_file target_file

The ln and symlink commands create a symbolic link at the target_file location pointing to the source_file location.

The mkdir command creates the directory named by the directory_name operand.

The pwd command returns the absolute pathname of the current working directory.

rename source target

The rename command renames the file or directory named by the source operand to the destination path named by the target operand.

The rm command removes the file specified by the file operand.

The rmdir command removes the directory entry specified by the directory operand, provided it is empty.

symlink source_file target_file

See ln. —random-file (SSL) Specify the path name to file containing what will be considered as random data. The data is used to seed the random engine for SSL connections. See also the —egd-file option. —raw (HTTP) When used, it disables all internal HTTP decoding of content or transfer encodings and instead makes them passed on unaltered, raw. (Added in 7.16.2) —remote-name-all This option changes the default action for all given URLs to be dealt with as if -O, —remote-name were used for each one. So if you want to disable that for a specific URL after —remote-name-all is used, you must use «-o —» or —no-remote-name. (Added in 7.19.0) —resolve Provide a custom address for a specific host and port pair. Using this, you can make the curl requests(s) use a specified address and prevent the otherwise normally resolved address to be used. Consider it a sort of /etc/hosts alternative provided on the command line. The port number should be the number used for the specific protocol the host will be used for. It means you need several entries if you want to provide address for the same host but different ports.

This option can be used many times to add many hostnames to resolve.

(Added in 7.21.3) -r, —range (HTTP/FTP) Retrieve a byte range (i.e a partial document) from an HTTP/1.1 or FTP server. Ranges can be specified in many ways.

0-499 specifies the first 500 bytes;

500-999 specifies the second 500 bytes;

-500 specifies the last 500 bytes;

9500- specifies the bytes from offset 9500 and forward;

0-0,-1 specifies the first and last byte only(*)(H);

500-700,600-799 specifies 300 bytes from offset 500(H);

100-199,500-599 specifies two separate 100 bytes ranges(*)(H).

(*) = NOTE that this causes the server to reply with a multipart response!

Also be aware that many HTTP/1.1 servers do not have this feature enabled, so that when you attempt to get a range, you’ll instead get the whole document.

FTP range downloads only support the simple syntax ‘start-stop‘ (optionally with one of the numbers omitted). It depends on the non-RFC command SIZE.

Only digit characters (0-9) are valid in the ‘start‘ and ‘stop‘ fields of the ‘start-stop‘ range syntax. If a non-digit character is given in the range, the server’s response will be unspecified, depending on the server’s configuration.

If this option is used several times, the last one will be used. -R, —remote-time When used, this makes libcurl attempt to figure out the timestamp of the remote file, and if that is available make the local file get that same timestamp. —retry If a transient error is returned when curl tries to perform a transfer, it retries this number of times before giving up. Setting the number to 0 makes curl do no retries (which is the default). Transient error means either: a timeout, an FTP 5xx response code or an HTTP 5xx response code.

When curl is about to retry a transfer, it first waits one second, and then for all forthcoming retries, it doubles the waiting time until it reaches 10 minutes, which then is the delay between the rest of the retries. Using —retry-delay, you disable this exponential backoff algorithm. See also —retry-max-time to limit the total time allowed for retries. (Added in 7.12.3)

If this option is used multiple times, the last occurrence decide the amount. —retry-delay Make curl sleep this amount of time between each retry when a transfer has failed with a transient error (it changes the default backoff time algorithm between retries). This option is only interesting if —retry is also used. Setting this delay to zero makes curl use the default backoff time. (Added in 7.12.3)

If this option is used multiple times, the last occurrence decide the amount. —retry-max-time The retry timer is reset before the first transfer attempt. Retries will be done as usual (see —retry) as long as the timer hasn’t reached this given limit. Notice that if the timer hasn’t reached the limit, the request will be made and while performing, it may take longer than this given time. To limit a single request’s maximum time, use -m, —max-time. Set this option to zero to not timeout retries. (Added in 7.12.3)

If this option is used multiple times, the last occurrence decide the amount. -s, —silent Silent mode. Don’t show progress meter or error messages. Makes curl mute. It still outputs the data you ask for, potentially even to the terminal/stdout unless you redirect it. —sasl-ir Enable initial response in SASL authentication. (Added in 7.31.0) -S, —show-error When used with -s, it makes curl show error message if it fails. —ssl (FTP, POP3, IMAP, SMTP) Try to use SSL/TLS for the connection. Reverts to a non-secure connection if the server doesn’t support SSL/TLS. See also —ftp-ssl-control and —ssl-reqd for different levels of encryption required. (Added in 7.20.0)

This option was formerly known as —ftp-ssl (Added in 7.11.0). That option name can still be used but will be removed in a future version. —ssl-reqd (FTP, POP3, IMAP, SMTP) Require SSL/TLS for the connection. Terminates the connection if the server doesn’t support SSL/TLS. (Added in 7.20.0)

This option was formerly known as —ftp-ssl-reqd (added in 7.15.5). That option name can still be used, but is removed in a future version. —ssl-allow-beast (SSL) This option tells curl not to work around a security flaw in the SSL3 and TLS1.0 protocols known as BEAST. If this option isn’t used, the SSL layer may use work-arounds known to cause interoperability problems with some older SSL implementations. WARNING: this option loosens the SSL security, and using this flag, you ask for exactly that. (Added in 7.25.0) —socks4

Use the specified SOCKS4 proxy. If the port number is not specified, it is assumed at port 1080. (Added in 7.15.2)

This option overrides any previous use of -x, —proxy, as they are mutually exclusive.

Since 7.21.7, this option is superfluous since you can specify a socks4 proxy with -x, —proxy using a socks4:// protocol prefix.

If this option is used several times, the last one is used. —socks4a

Use the specified SOCKS4a proxy. If the port number is not specified, it is assumed at port 1080. (Added in 7.18.0)

This option overrides any previous use of -x, —proxy, as they are mutually exclusive.

Since 7.21.7, this option is superfluous since you can specify a socks4a proxy with -x, —proxy using a socks4a:// protocol prefix.

If this option is used several times, the last one is used. —socks5-hostname

Use the specified SOCKS5 proxy (and let the proxy resolve the hostname). If the port number is not specified, it is assumed at port 1080. (Added in 7.18.0)

This option overrides any previous use of -x, —proxy, as they are mutually exclusive.

Since 7.21.7, this option is superfluous since you can specify a socks5 hostname proxy with -x, —proxy using a socks5h:// protocol prefix.

If this option is used several times, the last one is used. (This option was previously wrongly documented and used as —socks without the number appended.) —socks5

Use the specified SOCKS5 proxy — but resolve the hostname locally. If the port number is not specified, it is assumed at port 1080.

This option overrides any previous use of -x, —proxy, as they are mutually exclusive.

Since 7.21.7, this option is superfluous since you can specify a socks5 proxy with -x, —proxy using a socks5:// protocol prefix.

If this option is used several times, the last one is used. (This option was previously wrongly documented and used as —socks without the number appended.)

This option (and —socks4) does not work with IPV6, FTPS or LDAP. —socks5-gssapi-service The default service name for a socks server is rcmd/server-fqdn. This option allows you to change it.

—socks5 proxy-name —socks5-gssapi-service sockd

would use sockd/proxy-name;

—socks5 proxy-name —socks5-gssapi-service sockd/real-name

would use sockd/real-name for cases where the proxy-name does not match the principal name. —socks5-gssapi-nec As part of the gssapi negotiation a protection mode is negotiated. RFC 1961 says in section 4.3/4.4 it should be protected, but the NEC reference implementation does not. The option —socks5-gssapi-nec allows the unprotected exchange of the protection mode negotiation. (Added in 7.19.4). —stderr Redirect all writes to stderr to the specified file instead. If the file name is a plain ‘—‘, it is instead written to stdout.

If this option is used several times, the last one is used. —tcp-nodelay Turn on the TCP_NODELAY option. See the curl_easy_setopt man page for details about this option. (Added in 7.11.2) —tftp-blksize (TFTP) Set TFTP BLKSIZE option (must be >512). This is the block size that curl tries to use when transferring data to or from a TFTP server. By default, 512 bytes is used.

If this option is used several times, the last one is used.

(Added in 7.20.0) —tlsauthtype

Set TLS authentication type. Currently, the only supported option is «SRP», for TLS-SRP (RFC 5054). If —tlsuser and —tlspassword are specified but —tlsauthtype is not, then this option defaults to «SRP». (Added in 7.21.4) —tlsuser Set username for use with the TLS authentication method specified with —tlsauthtype. Requires that —tlspassword also be set. (Added in 7.21.4) —tlspassword Set password for use with the TLS authentication method specified with —tlsauthtype. Requires that —tlsuser also be set. (Added in 7.21.4) —tr-encoding (HTTP) Request a compressed Transfer-Encoding response using one of the algorithms curl supports, and uncompress the data while receiving it.

(Added in 7.21.6) -t, —telnet-option Pass options to the telnet protocol. Supported options are:

TType= Sets the terminal type.

XDISPLOC= Sets the X display location.

NEW_ENV= Sets an environment variable. -T, —upload-file 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. NOTE you must use a trailing / on the last directory to really prove to curl that there is no file name or curl thinks that your last directory name is the remote file name to use. That most likely causes the upload operation to fail. If this is used on a http(s) server, the PUT command is used.

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.

You can specify one -T for each URL on the command line. Each -T + URL pair specifies what to upload and to where. curl also supports «globbing» of the -T argument, meaning you can upload multiple files to a single URL using the same URL globbing style supported in the URL, like this:

curl -T «» http://www.uploadtothissite.com

curl -T «img259.png» ftp://ftp.picturemania.com/upload/ —trace Enables a full trace dump of all incoming and outgoing data, including descriptive information, to the given output file. Use «—» as filename to have the output sent to stdout.

This option overrides previous uses of -v, —verbose or —trace-ascii.

If this option is used several times, the last one is used. —trace-ascii Enables a full trace dump of all incoming and outgoing data, including descriptive information, to the given output file. Use «—» as filename to have the output sent to stdout.

This is very similar to —trace, but leaves out the hex part and only shows the ASCII part of the dump. It makes smaller output that might be easier to read for untrained humans.

This option overrides previous uses of -v, —verbose or —trace.

If this option is used several times, the last one is used. —trace-time Prepends a timestamp to each trace or verbose line that curl displays. (Added in 7.14.0) -u, —user Specify user and password to use for server authentication. Overrides -n, —netrc and —netrc-optional.

If you give the username (without entering a colon) curl prompts for a password.

If you use an SSPI-enabled curl binary and do NTLM authentication, you can force curl to pick up the username and password from your environment by specifying a single colon with this option: «-u :«.

If this option is used several times, the last one is used. -U, —proxy-user Specify user and password to use for proxy authentication.

If you use an SSPI-enabled curl binary and do NTLM authentication, you can force curl to pick up the username and password from your environment by specifying a single colon with this option: «-U :«.

Источник

Читайте также:  1с linux обновление платформы