{ "mode": "man", "parameter": "curl", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/curl/1/json", "generated": "2026-08-09T11:59:37Z", "synopsis": "", "sections": { "NAME": { "content": "curl - transfer a URL\n", "subsections": [] }, "SYNOPSIS": { "content": "", "subsections": [ { "name": "curl [options / URLs]", "content": "" } ] }, "DESCRIPTION": { "content": "curl is a tool for transferring data from or to a server using URLs. It supports these proto‐\ncols: DICT, FILE, FTP, FTPS, GOPHER, GOPHERS, HTTP, HTTPS, IMAP, IMAPS, LDAP, LDAPS, MQTT,\nPOP3, POP3S, RTMP, RTMPS, RTSP, SCP, SFTP, SMB, SMBS, SMTP, SMTPS, TELNET, TFTP, WS and WSS.\n\ncurl is powered by libcurl for all transfer-related features. See libcurl(3) for details.\n", "subsections": [] }, "URL": { "content": "The URL syntax is protocol-dependent. You find a detailed description in RFC 3986.\n\nIf you provide a URL without a leading protocol:// scheme, curl guesses what protocol you\nwant. It then defaults to HTTP but assumes others based on often-used host name prefixes. For\nexample, for host names starting with \"ftp.\" curl assumes you want FTP.\n\nYou can specify any amount of URLs on the command line. They are fetched in a sequential man‐\nner in the specified order unless you use -Z, --parallel. You can specify command line op‐\ntions and URLs mixed and in any order on the command line.\n\ncurl attempts to reuse connections when doing multiple transfers, so that getting many files\nfrom the same server do not use multiple connects and setup handshakes. This improves speed.\nConnection reuse can only be done for URLs specified for a single command line invocation and\ncannot be performed between separate curl runs.\n\nProvide an IPv6 zone id in the URL with an escaped percentage sign. Like in\n\n\"http://[fe80::3%25eth0]/\"\n\nEverything provided on the command line that is not a command line option or its argument,\ncurl assumes is a URL and treats it as such.\n", "subsections": [] }, "GLOBBING": { "content": "You can specify multiple URLs or parts of URLs by writing lists within braces or ranges\nwithin brackets. We call this \"globbing\".\n\nProvide a list with three different names like this:\n\n\"http://site.{one,two,three}.com\"\n\nor you can get sequences of alphanumeric series by using [] as in:\n\n\"ftp://ftp.example.com/file[1-100].txt\"\n\n\"ftp://ftp.example.com/file[001-100].txt\" (with leading zeros)\n\n\"ftp://ftp.example.com/file[a-z].txt\"\n\nNested sequences are not supported, but you can use several ones next to each other:\n\n\"http://example.com/archive[1996-1999]/vol[1-4]/part{a,b,c}.html\"\n\nYou can specify a step counter for the ranges to get every Nth number or letter:\n\n\"http://example.com/file[1-100:10].txt\"\n\n\"http://example.com/file[a-z:2].txt\"\n\nWhen using [] or {} sequences when invoked from a command line prompt, you probably have to\nput the full URL within double quotes to avoid the shell from interfering with it. This also\ngoes for other characters treated special, like for example '&', '?' and '*'.\n\nSwitch off globbing with -g, --globoff.\n", "subsections": [] }, "VARIABLES": { "content": "curl supports command line variables (added in 8.3.0). Set variables with --variable\nname=content or --variable name@file (where \"file\" can be stdin if set to a single dash (-)).\n\nVariable contents can expanded in option parameters using \"{{name}}\" (without the quotes) if\nthe option name is prefixed with \"--expand-\". This gets the contents of the variable \"name\"\ninserted, or a blank if the name does not exist as a variable. Insert \"{{\" verbatim in the\nstring by prefixing it with a backslash, like \"\\{{\".\n\nYou an access and expand environment variables by first importing them. You can select to ei‐\nther require the environment variable to be set or you can provide a default value in case it\nis not already set. Plain --variable %name imports the variable called 'name' but exits with\nan error if that environment variable is not already set. To provide a default value if it is\nnot set, use --variable %name=content or --variable %name@content.\n\nExample. Get the USER environment variable into the URL, fail if USER is not set:\n\n--variable '%USER'\n--expand-url = \"https://example.com/api/{{USER}}/method\"\n\nWhen expanding variables, curl supports a set of functions that can make the variable con‐\ntents more convenient to use. It can trim leading and trailing white space with trim, it can\noutput the contents as a JSON quoted string with json, URL encode the string with url or\nbase64 encode it with b64. You apply function to a variable expansion, add them colon sepa‐\nrated to the right side of the variable. Variable content holding null bytes that are not en‐\ncoded when expanded cause error.\n\nExample: get the contents of a file called $HOME/.secret into a variable called \"fix\". Make\nsure that the content is trimmed and percent-encoded sent as POST data:\n\n--variable %HOME\n--expand-variable fix@{{HOME}}/.secret\n--expand-data \"{{fix:trim:url}}\"\nhttps://example.com/\n\nCommand line variables and expansions were added in in 8.3.0.\n", "subsections": [] }, "OUTPUT": { "content": "If not told otherwise, curl writes the received data to stdout. It can be instructed to in‐\nstead save that data into a local file, using the -o, --output or -O, --remote-name options.\nIf curl is given multiple URLs to transfer on the command line, it similarly needs multiple\noptions for where to save them.\n\ncurl does not parse or otherwise \"understand\" the content it gets or writes as output. It\ndoes no encoding or decoding, unless explicitly asked to with dedicated command line options.\n", "subsections": [] }, "PROTOCOLS": { "content": "curl supports numerous protocols, or put in URL terms: schemes. Your particular build may not\nsupport them all.\n\nDICT Lets you lookup words using online dictionaries.\n\nFILE Read or write local files. curl does not support accessing file:// URL remotely, but\nwhen running on Microsoft Windows using the native UNC approach works.\n\nFTP(S) curl supports the File Transfer Protocol with a lot of tweaks and levers. With or\nwithout using TLS.\n\nGOPHER(S)\nRetrieve files.\n\nHTTP(S)\ncurl supports HTTP with numerous options and variations. It can speak HTTP version\n0.9, 1.0, 1.1, 2 and 3 depending on build options and the correct command line op‐\ntions.\n\nIMAP(S)\nUsing the mail reading protocol, curl can \"download\" emails for you. With or without\nusing TLS.\n\nLDAP(S)\ncurl can do directory lookups for you, with or without TLS.\n\nMQTT curl supports MQTT version 3. Downloading over MQTT equals \"subscribe\" to a topic\nwhile uploading/posting equals \"publish\" on a topic. MQTT over TLS is not supported\n(yet).\n\nPOP3(S)\nDownloading from a pop3 server means getting a mail. With or without using TLS.\n\nRTMP(S)\nThe Realtime Messaging Protocol is primarily used to serve streaming media and curl\ncan download it.\n\nRTSP curl supports RTSP 1.0 downloads.\n\nSCP curl supports SSH version 2 scp transfers.\n\nSFTP curl supports SFTP (draft 5) done over SSH version 2.\n\nSMB(S) curl supports SMB version 1 for upload and download.\n\nSMTP(S)\nUploading contents to an SMTP server means sending an email. With or without TLS.\n\nTELNET Telling curl to fetch a telnet URL starts an interactive session where it sends what\nit reads on stdin and outputs what the server sends it.\n\nTFTP curl can do TFTP downloads and uploads.\n", "subsections": [] }, "PROGRESS METER": { "content": "curl normally displays a progress meter during operations, indicating the amount of trans‐\nferred data, transfer speeds and estimated time left, etc. The progress meter displays the\ntransfer rate in bytes per second. The suffixes (k, M, G, T, P) are 1024 based. For example\n1k is 1024 bytes. 1M is 1048576 bytes.\n\ncurl displays this data to the terminal by default, so if you invoke curl to do an operation\nand it is about to write data to the terminal, it disables the progress meter as otherwise it\nwould mess up the output mixing progress meter and response data.\n\nIf you want a progress meter for HTTP POST or PUT requests, you need to redirect the response\noutput to a file, using shell redirect (>), -o, --output or similar.\n\nThis does not apply to FTP upload as that operation does not spit out any response data to\nthe terminal.\n\nIf you prefer a progress \"bar\" instead of the regular meter, -#, --progress-bar is your\nfriend. You can also disable the progress meter completely with the -s, --silent option.\n", "subsections": [] }, "VERSION": { "content": "This man page describes curl 8.5.0. If you use a later version, chances are this man page\ndoes not fully document it. If you use an earlier version, this document tries to include\nversion information about which specific version that introduced changes.\n\nYou can always learn which the latest curl version is by running\n\ncurl https://curl.se/info\n\nThe online version of this man page is always showing the latest incarnation:\nhttps://curl.se/docs/manpage.html\n", "subsections": [] }, "OPTIONS": { "content": "Options start with one or two dashes. Many of the options require an additional value next to\nthem. If provided text does not start with a dash, it is presumed to be and treated as a URL.\n\nThe short \"single-dash\" form of the options, -d for example, may be used with or without a\nspace between it and its value, although a space is a recommended separator. The long \"dou‐\nble-dash\" form, -d, --data for example, requires a space between it and its value.\n\nShort version options that do not need any additional values can be used immediately next to\neach other, like for example you can specify all the options -O, -L and -v at once as -OLv.\n\nIn general, all boolean options are enabled with --option and yet again disabled with\n--no-option. That is, you use the same option name but prefix it with \"no-\". However, in this\nlist we mostly only list and show the --option version of them.\n\nWhen -:, --next is used, it resets the parser state and you start again with a clean option\nstate, except for the options that are \"global\". Global options retain their values and mean‐\ning even after -:, --next.\n\nThe following options are global: --fail-early, --libcurl, --parallel-immediate, -Z, --paral‐\nlel, -#, --progress-bar, --rate, -S, --show-error, --stderr, --styled-output, --trace-ascii,\n--trace-config, --trace-ids, --trace-time, --trace and -v, --verbose.\n", "subsections": [ { "name": "--abstract-unix-socket ", "content": "(HTTP) Connect through an abstract Unix domain socket, instead of using the network.\nNote: netstat shows the path of an abstract socket prefixed with '@', however the\n argument should not have this leading character.\n\nIf --abstract-unix-socket is provided several times, the last set value is used.\n\nExample:\ncurl --abstract-unix-socket socketpath https://example.com\n\nSee also --unix-socket. Added in 7.53.0.\n", "long": "--abstract-unix-socket", "arg": "" }, { "name": "--alt-svc ", "content": "(HTTPS) This option enables the alt-svc parser in curl. If the file name points to an\nexisting alt-svc cache file, that gets used. After a completed transfer, the cache is\nsaved to the file name again if it has been modified.\n\nSpecify a \"\" file name (zero length) to avoid loading/saving and make curl just handle\nthe cache in memory.\n\nIf this option is used several times, curl loads contents from all the files but the\nlast one is used for saving.\n\n--alt-svc can be used several times in a command line\n\nExample:\ncurl --alt-svc svc.txt https://example.com\n\nSee also --resolve and --connect-to. Added in 7.64.1.\n", "long": "--alt-svc" }, { "name": "--anyauth", "content": "(HTTP) Tells curl to figure out authentication method by itself, and use the most se‐\ncure one the remote site claims to support. This is done by first doing a request and\nchecking the response-headers, thus possibly inducing an extra network round-trip.\nThis is used instead of setting a specific authentication method, which you can do\nwith --basic, --digest, --ntlm, and --negotiate.\n\nUsing --anyauth is not recommended if you do uploads from stdin, since it may require\ndata to be sent twice and then the client must be able to rewind. If the need should\narise when uploading from stdin, the upload operation fails.\n\nUsed together with -u, --user.\n\nProviding --anyauth multiple times has no extra effect.\n\nExample:\ncurl --anyauth --user me:pwd https://example.com\n\nSee also --proxy-anyauth, --basic and --digest.\n", "long": "--anyauth" }, { "name": "-a, --append", "content": "(FTP SFTP) When used in an upload, this option makes curl append to the target file\ninstead of overwriting it. If the remote file does not exist, it is created. Note that\nthis flag is ignored by some SFTP servers (including OpenSSH).\n\nProviding -a, --append multiple times has no extra effect. Disable it again with\n--no-append.\n\nExample:\ncurl --upload-file local --append ftp://example.com/\n\nSee also -r, --range and -C, --continue-at.\n\n--aws-sigv4 \nUse AWS V4 signature authentication in the transfer.\n\nThe provider argument is a string that is used by the algorithm when creating outgoing\nauthentication headers.\n\nThe region argument is a string that points to a geographic area of a resources col‐\nlection (region-code) when the region name is omitted from the endpoint.\n\nThe service argument is a string that points to a function provided by a cloud (ser‐\nvice-code) when the service name is omitted from the endpoint.\n\nIf --aws-sigv4 is provided several times, the last set value is used.\n\nExample:\ncurl --aws-sigv4 \"aws:amz:us-east-2:es\" --user \"key:secret\" https://example.com\n\nSee also --basic and -u, --user. Added in 7.75.0.\n", "flag": "-a", "long": "--append" }, { "name": "--basic", "content": "(HTTP) Tells curl to use HTTP Basic authentication with the remote host. This is the\ndefault and this option is usually pointless, unless you use it to override a previ‐\nously set option that sets a different authentication method (such as --ntlm, --di‐\ngest, or --negotiate).\n\nUsed together with -u, --user.\n\nProviding --basic multiple times has no extra effect.\n\nExample:\ncurl -u name:password --basic https://example.com\n\nSee also --proxy-basic.\n", "long": "--basic" }, { "name": "--ca-native", "content": "(TLS) Tells curl to use the CA store from the native operating system to verify the\npeer. By default, curl otherwise uses a CA store provided in a single file or direc‐\ntory, but when using this option it interfaces the operating system's own vault.\n\nThis option only works for curl on Windows when built to use OpenSSL. When curl on\nWindows is built to use Schannel, this feature is implied and curl then only uses the\nnative CA store.\n\ncurl built with wolfSSL also supports this option (added in 8.3.0).\n\nProviding --ca-native multiple times has no extra effect. Disable it again with\n--no-ca-native.\n\nExample:\ncurl --ca-native https://example.com\n\nSee also --cacert, --capath and -k, --insecure. Added in 8.2.0.\n", "long": "--ca-native" }, { "name": "--cacert ", "content": "(TLS) Tells curl to use the specified certificate file to verify the peer. The file\nmay contain multiple CA certificates. The certificate(s) must be in PEM format. Nor‐\nmally curl is built to use a default file for this, so this option is typically used\nto alter that default file.\n\ncurl recognizes the environment variable named 'CURLCABUNDLE' if it is set, and uses\nthe given path as a path to a CA cert bundle. This option overrides that variable.\n\nThe windows version of curl automatically looks for a CA certs file named\n'curl-ca-bundle.crt', either in the same directory as curl.exe, or in the Current\nWorking Directory, or in any folder along your PATH.\n\n(iOS and macOS only) If curl is built against Secure Transport, then this option is\nsupported for backward compatibility with other SSL engines, but it should not be set.\nIf the option is not set, then curl uses the certificates in the system and user Key‐\nchain to verify the peer, which is the preferred method of verifying the peer's cer‐\ntificate chain.\n\n(Schannel only) This option is supported for Schannel in Windows 7 or later (added in\n7.60.0). This option is supported for backward compatibility with other SSL engines;\ninstead it is recommended to use Windows' store of root certificates (the default for\nSchannel).\n\nIf --cacert is provided several times, the last set value is used.\n\nExample:\ncurl --cacert CA-file.txt https://example.com\n\nSee also --capath and -k, --insecure.\n", "long": "--cacert", "arg": "" }, { "name": "--capath ", "content": "(TLS) Tells curl to use the specified certificate directory to verify the peer. Multi‐\nple paths can be provided by separating them with \":\" (e.g. \"path1:path2:path3\"). The\ncertificates must be in PEM format, and if curl is built against OpenSSL, the direc‐\ntory must have been processed using the crehash utility supplied with OpenSSL. Using\n--capath can allow OpenSSL-powered curl to make SSL-connections much more efficiently\nthan using --cacert if the --cacert file contains many CA certificates.\n\nIf this option is set, the default capath value is ignored.\n\nIf --capath is provided several times, the last set value is used.\n\nExample:\ncurl --capath /local/directory https://example.com\n\nSee also --cacert and -k, --insecure.\n", "long": "--capath", "arg": "" }, { "name": "--cert-status", "content": "(TLS) Tells curl to verify the status of the server certificate by using the Certifi‐\ncate Status Request (aka. OCSP stapling) TLS extension.\n\nIf this option is enabled and the server sends an invalid (e.g. expired) response, if\nthe response suggests that the server certificate has been revoked, or no response at\nall is received, the verification fails.\n\nThis is currently only implemented in the OpenSSL and GnuTLS backends.\n\nProviding --cert-status multiple times has no extra effect. Disable it again with\n--no-cert-status.\n\nExample:\ncurl --cert-status https://example.com\n\nSee also --pinnedpubkey.\n", "long": "--cert-status" }, { "name": "--cert-type ", "content": "(TLS) Tells curl what type the provided client certificate is using. PEM, DER, ENG and\nP12 are recognized types.\n\nThe default type depends on the TLS backend and is usually PEM, however for Secure\nTransport and Schannel it is P12. If -E, --cert is a pkcs11: URI then ENG is the de‐\nfault type.\n\nIf --cert-type is provided several times, the last set value is used.\n\nExample:\ncurl --cert-type PEM --cert file https://example.com\n\nSee also -E, --cert, --key and --key-type.\n\n-E, --cert \n(TLS) Tells curl to use the specified client certificate file when getting a file with\nHTTPS, FTPS or another SSL-based protocol. The certificate must be in PKCS#12 format\nif using Secure Transport, or PEM format if using any other engine. If the optional\npassword is not specified, it is queried for on the terminal. Note that this option\nassumes a certificate file that is the private key and the client certificate concate‐\nnated. See -E, --cert and --key to specify them independently.\n\nIn the portion of the argument, you must escape the character \":\" as\n\"\\:\" so that it is not recognized as the password delimiter. Similarly, you must es‐\ncape the character \"\\\" as \"\\\\\" so that it is not recognized as an escape character.\n\nIf curl is built against OpenSSL library, and the engine pkcs11 is available, then a\nPKCS#11 URI (RFC 7512) can be used to specify a certificate located in a PKCS#11 de‐\nvice. A string beginning with \"pkcs11:\" is interpreted as a PKCS#11 URI. If a PKCS#11\nURI is provided, then the --engine option is set as \"pkcs11\" if none was provided and\nthe --cert-type option is set as \"ENG\" if none was provided.\n\n(iOS and macOS only) If curl is built against Secure Transport, then the certificate\nstring can either be the name of a certificate/private key in the system or user key‐\nchain, or the path to a PKCS#12-encoded certificate and private key. If you want to\nuse a file from the current directory, please precede it with \"./\" prefix, in order to\navoid confusion with a nickname.\n\n(Schannel only) Client certificates must be specified by a path expression to a cer‐\ntificate store. (Loading PFX is not supported; you can import it to a store first).\nYou can use \"\\\\\" to refer to a certificate in\nthe system certificates store, for example, \"Curren‐\ntUser\\MY\\934a7ac6f8a5d579285a74fa61e19f23ddfe8d7a\". Thumbprint is usually a SHA-1 hex\nstring which you can see in certificate details. Following store locations are sup‐\nported: CurrentUser, LocalMachine, CurrentService, Services, CurrentUserGroupPolicy,\nLocalMachineGroupPolicy and LocalMachineEnterprise.\n\nIf -E, --cert is provided several times, the last set value is used.\n\nExample:\ncurl --cert certfile --key keyfile https://example.com\n\nSee also --cert-type, --key and --key-type.\n", "long": "--cert-type", "arg": "" }, { "name": "--ciphers ", "content": "(TLS) Specifies which ciphers to use in the connection. The list of ciphers must spec‐\nify valid ciphers. Read up on SSL cipher list details on this URL:\n\nhttps://curl.se/docs/ssl-ciphers.html\n\nIf --ciphers is provided several times, the last set value is used.\n\nExample:\ncurl --ciphers ECDHE-ECDSA-AES256-CCM8 https://example.com\n\nSee also --tlsv1.3, --tls13-ciphers and --proxy-ciphers.\n", "long": "--ciphers" }, { "name": "--compressed-ssh", "content": "(SCP SFTP) Enables built-in SSH compression. This is a request, not an order; the\nserver may or may not do it.\n\nProviding --compressed-ssh multiple times has no extra effect. Disable it again with\n--no-compressed-ssh.\n\nExample:\ncurl --compressed-ssh sftp://example.com/\n\nSee also --compressed. Added in 7.56.0.\n", "long": "--compressed-ssh" }, { "name": "--compressed", "content": "(HTTP) Request a compressed response using one of the algorithms curl supports, and\nautomatically decompress the content.\n\nResponse headers are not modified when saved, so if they are \"interpreted\" separately\nagain at a later point they might appear to be saying that the content is (still) com‐\npressed; while in fact it has already been decompressed.\n\nIf this option is used and the server sends an unsupported encoding, curl reports an\nerror. This is a request, not an order; the server may or may not deliver data com‐\npressed.\n\nProviding --compressed multiple times has no extra effect. Disable it again with\n--no-compressed.\n\nExample:\ncurl --compressed https://example.com\n\nSee also --compressed-ssh.\n", "long": "--compressed" }, { "name": "-K, --config ", "content": "Specify a text file to read curl arguments from. The command line arguments found in\nthe text file are used as if they were provided on the command line.\n\nOptions and their parameters must be specified on the same line in the file, separated\nby whitespace, colon, or the equals sign. Long option names can optionally be given in\nthe config file without the initial double dashes and if so, the colon or equals char‐\nacters can be used as separators. If the option is specified with one or two dashes,\nthere can be no colon or equals character between the option and its parameter.\n\nIf the parameter contains whitespace or starts with a colon (:) or equals sign (=), it\nmust be specified enclosed within double quotes (\"). Within double quotes the follow‐\ning escape sequences are available: \\\\, \\\", \\t, \\n, \\r and \\v. A backslash preceding\nany other letter is ignored.\n\nIf the first non-blank column of a config line is a '#' character, that line is\ntreated as a comment.\n\nOnly write one option per physical line in the config file. A single line is required\nto be no more than 10 megabytes (since 8.2.0).\n\nSpecify the filename to -K, --config as '-' to make curl read the file from stdin.\n\nNote that to be able to specify a URL in the config file, you need to specify it using\nthe --url option, and not by simply writing the URL on its own line. So, it could look\nsimilar to this:\n\nurl = \"https://curl.se/docs/\"\n\n# --- Example file ---\n# this is a comment\nurl = \"example.com\"\noutput = \"curlhere.html\"\nuser-agent = \"superagent/1.0\"\n\n# and fetch another URL too\nurl = \"example.com/docs/manpage.html\"\n-O\nreferer = \"http://nowhereatall.example.com/\"\n# --- End of example file ---\n\nWhen curl is invoked, it (unless -q, --disable is used) checks for a default config\nfile and uses it if found, even when -K, --config is used. The default config file is\nchecked for in the following places in this order:\n\n1) \"$CURLHOME/.curlrc\"\n\n2) \"$XDGCONFIGHOME/curlrc\" (Added in 7.73.0)\n\n3) \"$HOME/.curlrc\"\n\n4) Windows: \"%USERPROFILE%\\.curlrc\"\n\n5) Windows: \"%APPDATA%\\.curlrc\"\n\n6) Windows: \"%USERPROFILE%\\Application Data\\.curlrc\"\n\n7) Non-Windows: use getpwuid to find the home directory\n\n8) On Windows, if it finds no .curlrc file in the sequence described above, it checks\nfor one in the same dir the curl executable is placed.\n\nOn Windows two filenames are checked per location: .curlrc and curlrc, preferring the\nformer. Older versions on Windows checked for curlrc only.\n\n-K, --config can be used several times in a command line\n\nExample:\ncurl --config file.txt https://example.com\n\nSee also -q, --disable.\n", "flag": "-K", "long": "--config", "arg": "" }, { "name": "--connect-timeout ", "content": "Maximum time in seconds that you allow curl's connection to take. This only limits\nthe connection phase, so if curl connects within the given period it continues - if\nnot it exits.\n\nThis option accepts decimal values. The decimal value needs to be provided using a dot\n(.) as decimal separator - not the local version even if it might be using another\nseparator.\n\nThe connection phase is considered complete when the DNS lookup and requested TCP, TLS\nor QUIC handshakes are done.\n\nIf --connect-timeout is provided several times, the last set value is used.\n\nExamples:\ncurl --connect-timeout 20 https://example.com\ncurl --connect-timeout 3.14 https://example.com\n\nSee also -m, --max-time.\n", "long": "--connect-timeout" }, { "name": "--connect-to ", "content": "For a request to the given HOST1:PORT1 pair, connect to HOST2:PORT2 instead. This op‐\ntion is suitable to direct requests at a specific server, e.g. at a specific cluster\nnode in a cluster of servers. This option is only used to establish the network con‐\nnection. It does NOT affect the hostname/port that is used for TLS/SSL (e.g. SNI, cer‐\ntificate verification) or for the application protocols. \"HOST1\" and \"PORT1\" may be\nthe empty string, meaning \"any host/port\". \"HOST2\" and \"PORT2\" may also be the empty\nstring, meaning \"use the request's original host/port\".\n\nA \"host\" specified to this option is compared as a string, so it needs to match the\nname used in request URL. It can be either numerical such as \"127.0.0.1\" or the full\nhost name such as \"example.org\".\n\n--connect-to can be used several times in a command line\n\nExample:\ncurl --connect-to example.com:443:example.net:8443 https://example.com\n\nSee also --resolve and -H, --header.\n", "long": "--connect-to", "arg": "" }, { "name": "-C, --continue-at ", "content": "Continue/Resume a previous file transfer at the given offset. The given offset is the\nexact number of bytes that are skipped, counting from the beginning of the source file\nbefore it is transferred to the destination. If used with uploads, the FTP server com‐\nmand SIZE is not used by curl.\n\nUse \"-C -\" to tell curl to automatically find out where/how to resume the transfer. It\nthen uses the given output/input files to figure that out.\n\nIf -C, --continue-at is provided several times, the last set value is used.\n\nExamples:\ncurl -C - https://example.com\ncurl -C 400 https://example.com\n\nSee also -r, --range.\n", "flag": "-C", "long": "--continue-at", "arg": "" }, { "name": "-c, --cookie-jar ", "content": "(HTTP) Specify to which file you want curl to write all cookies after a completed op‐\neration. Curl writes all cookies from its in-memory cookie storage to the given file\nat the end of operations. If no cookies are known, no data is written. The file is\ncreated using the Netscape cookie file format. If you set the file name to a single\ndash, \"-\", the cookies are written to stdout.\n\nThe file specified with -c, --cookie-jar is only used for output. No cookies are read\nfrom the file. To read cookies, use the -b, --cookie option. Both options can specify\nthe same file.\n\nThis command line option activates the cookie engine that makes curl record and use\ncookies. The -b, --cookie option also activates it.\n\nIf the cookie jar cannot be created or written to, the whole curl operation does not\nfail or even report an error clearly. Using -v, --verbose gets a warning displayed,\nbut that is the only visible feedback you get about this possibly lethal situation.\n\nIf -c, --cookie-jar is provided several times, the last set value is used.\n\nExamples:\ncurl -c store-here.txt https://example.com\ncurl -c store-here.txt -b read-these https://example.com\n\nSee also -b, --cookie.\n", "flag": "-c", "long": "--cookie-jar", "arg": "" }, { "name": "-b, --cookie ", "content": "(HTTP) Pass the data to the HTTP server in the Cookie header. It is supposedly the\ndata previously received from the server in a \"Set-Cookie:\" line. The data should be\nin the format \"NAME1=VALUE1; NAME2=VALUE2\". This makes curl use the cookie header with\nthis content explicitly in all outgoing request(s). If multiple requests are done due\nto authentication, followed redirects or similar, they all get this cookie passed on.\n\nIf no '=' symbol is used in the argument, it is instead treated as a filename to read\npreviously stored cookie from. This option also activates the cookie engine which\nmakes curl record incoming cookies, which may be handy if you are using this in combi‐\nnation with the -L, --location option or do multiple URL transfers on the same invoke.\nIf the file name is exactly a minus (\"-\"), curl instead reads the contents from stdin.\n\nThe file format of the file to read cookies from should be plain HTTP headers\n(Set-Cookie style) or the Netscape/Mozilla cookie file format.\n\nThe file specified with -b, --cookie is only used as input. No cookies are written to\nthe file. To store cookies, use the -c, --cookie-jar option.\n\nIf you use the Set-Cookie file format and do not specify a domain then the cookie is\nnot sent since the domain never matches. To address this, set a domain in Set-Cookie\nline (doing that includes subdomains) or preferably: use the Netscape format.\n\nUsers often want to both read cookies from a file and write updated cookies back to a\nfile, so using both -b, --cookie and -c, --cookie-jar in the same command line is com‐\nmon.\n\n-b, --cookie can be used several times in a command line\n\nExamples:\ncurl -b cookiefile https://example.com\ncurl -b cookiefile -c cookiefile https://example.com\n\nSee also -c, --cookie-jar and -j, --junk-session-cookies.\n", "flag": "-b", "long": "--cookie", "arg": "" }, { "name": "--create-dirs", "content": "When used in conjunction with the -o, --output option, curl creates the necessary lo‐\ncal directory hierarchy as needed. This option creates the directories mentioned with\nthe -o, --output option combined with the path possibly set with --output-dir. If the\ncombined output file name uses no directory, or if the directories it mentions already\nexist, no directories are created.\n\nCreated directories are made with mode 0750 on unix style file systems.\n\nTo create remote directories when using FTP or SFTP, try --ftp-create-dirs.\n\nProviding --create-dirs multiple times has no extra effect. Disable it again with\n--no-create-dirs.\n\nExample:\ncurl --create-dirs --output local/dir/file https://example.com\n\nSee also --ftp-create-dirs and --output-dir.\n", "long": "--create-dirs" }, { "name": "--create-file-mode ", "content": "(SFTP SCP FILE) When curl is used to create files remotely using one of the supported\nprotocols, this option allows the user to set which 'mode' to set on the file at cre‐\nation time, instead of the default 0644.\n\nThis option takes an octal number as argument.\n\nIf --create-file-mode is provided several times, the last set value is used.\n\nExample:\ncurl --create-file-mode 0777 -T localfile sftp://example.com/new\n\nSee also --ftp-create-dirs. Added in 7.75.0.\n\n--crlf (FTP SMTP) Convert line feeds to carriage return plus line feeds in upload. Useful for\nMVS (OS/390).\n\n(SMTP added in 7.40.0)\n\nProviding --crlf multiple times has no extra effect. Disable it again with --no-crlf.\n\nExample:\ncurl --crlf -T file ftp://example.com/\n\nSee also -B, --use-ascii.\n", "long": "--create-file-mode", "arg": "" }, { "name": "--crlfile ", "content": "(TLS) Provide a file using PEM format with a Certificate Revocation List that may\nspecify peer certificates that are to be considered revoked.\n\nIf --crlfile is provided several times, the last set value is used.\n\nExample:\ncurl --crlfile rejects.txt https://example.com\n\nSee also --cacert and --capath.\n", "long": "--crlfile", "arg": "" }, { "name": "--curves ", "content": "(TLS) Tells curl to request specific curves to use during SSL session establishment\naccording to RFC 8422, 5.1. Multiple algorithms can be provided by separating them\nwith \":\" (e.g. \"X25519:P-521\"). The parameter is available identically in the\n\"openssl sclient/sserver\" utilities.\n\n--curves allows a OpenSSL powered curl to make SSL-connections with exactly the (EC)\ncurve requested by the client, avoiding nontransparent client/server negotiations.\n\nIf this option is set, the default curves list built into OpenSSL are ignored.\n\nIf --curves is provided several times, the last set value is used.\n\nExample:\ncurl --curves X25519 https://example.com\n\nSee also --ciphers. Added in 7.73.0.\n", "long": "--curves" }, { "name": "--data-ascii ", "content": "(HTTP) This is just an alias for -d, --data.\n\n--data-ascii can be used several times in a command line\n\nExample:\ncurl --data-ascii @file https://example.com\n\nSee also --data-binary, --data-raw and --data-urlencode.\n", "long": "--data-ascii", "arg": "" }, { "name": "--data-binary ", "content": "(HTTP) This posts data exactly as specified with no extra processing whatsoever.\n\nIf you start the data with the letter @, the rest should be a filename. Data is posted\nin a similar manner as -d, --data does, except that newlines and carriage returns are\npreserved and conversions are never done.\n\nLike -d, --data the default content-type sent to the server is applica‐\ntion/x-www-form-urlencoded. If you want the data to be treated as arbitrary binary\ndata by the server then set the content-type to octet-stream: -H \"Content-Type: appli‐\ncation/octet-stream\".\n\nIf this option is used several times, the ones following the first append data as de‐\nscribed in -d, --data.\n\n--data-binary can be used several times in a command line\n\nExample:\ncurl --data-binary @filename https://example.com\n\nSee also --data-ascii.\n", "long": "--data-binary", "arg": "" }, { "name": "--data-raw ", "content": "(HTTP) This posts data similarly to -d, --data but without the special interpretation\nof the @ character.\n\n--data-raw can be used several times in a command line\n\nExamples:\ncurl --data-raw \"hello\" https://example.com\ncurl --data-raw \"@at@at@\" https://example.com\n\nSee also -d, --data.\n", "long": "--data-raw", "arg": "" }, { "name": "--data-urlencode ", "content": "(HTTP) This posts data, similar to the other -d, --data options with the exception\nthat this performs URL-encoding.\n\nTo be CGI-compliant, the part should begin with a name followed by a separator\nand a content specification. The part can be passed to curl using one of the\nfollowing syntaxes:\n\ncontent\nThis makes curl URL-encode the content and pass that on. Just be careful so\nthat the content does not contain any = or @ symbols, as that makes the syntax\nmatch one of the other cases below!\n\n=content\nThis makes curl URL-encode the content and pass that on. The preceding = symbol\nis not included in the data.\n\nname=content\nThis makes curl URL-encode the content part and pass that on. Note that the\nname part is expected to be URL-encoded already.\n\n@filename\nThis makes curl load data from the given file (including any newlines), URL-en‐\ncode that data and pass it on in the POST.\n\nname@filename\nThis makes curl load data from the given file (including any newlines), URL-en‐\ncode that data and pass it on in the POST. The name part gets an equal sign ap‐\npended, resulting in name=urlencoded-file-content. Note that the name is ex‐\npected to be URL-encoded already.\n\n--data-urlencode can be used several times in a command line\n\nExamples:\ncurl --data-urlencode name=val https://example.com\ncurl --data-urlencode =encodethis https://example.com\ncurl --data-urlencode name@file https://example.com\ncurl --data-urlencode @fileonly https://example.com\n\nSee also -d, --data and --data-raw.\n", "long": "--data-urlencode", "arg": "" }, { "name": "-d, --data ", "content": "(HTTP MQTT) Sends the specified data in a POST request to the HTTP server, in the same\nway that a browser does when a user has filled in an HTML form and presses the submit\nbutton. This makes curl pass the data to the server using the content-type applica‐\ntion/x-www-form-urlencoded. Compare to -F, --form.\n\n--data-raw is almost the same but does not have a special interpretation of the @\ncharacter. To post data purely binary, you should instead use the --data-binary op‐\ntion. To URL-encode the value of a form field you may use --data-urlencode.\n\nIf any of these options is used more than once on the same command line, the data\npieces specified are merged with a separating &-symbol. Thus, using '-d name=daniel -d\nskill=lousy' would generate a post chunk that looks like 'name=daniel&skill=lousy'.\n\nIf you start the data with the letter @, the rest should be a file name to read the\ndata from, or - if you want curl to read the data from stdin. Posting data from a file\nnamed 'foobar' would thus be done with -d, --data @foobar. When -d, --data is told to\nread from a file like that, carriage returns and newlines are stripped out. If you do\nnot want the @ character to have a special interpretation use --data-raw instead.\n\nThe data for this option is passed on to the server exactly as provided on the command\nline. curl does not convert, change or improve it. It is up to the user to provide the\ndata in the correct form.\n\n-d, --data can be used several times in a command line\n\nExamples:\ncurl -d \"name=curl\" https://example.com\ncurl -d \"name=curl\" -d \"tool=cmdline\" https://example.com\ncurl -d @filename https://example.com\n\nSee also --data-binary, --data-urlencode and --data-raw. This option is mutually ex‐\nclusive to -F, --form and -I, --head and -T, --upload-file.\n", "flag": "-d", "long": "--data", "arg": "" }, { "name": "--delegation ", "content": "(GSS/kerberos) Set LEVEL to tell the server what it is allowed to delegate when it\ncomes to user credentials.\n\nnone Do not allow any delegation.\n\npolicy Delegates if and only if the OK-AS-DELEGATE flag is set in the Kerberos service\nticket, which is a matter of realm policy.\n\nalways Unconditionally allow the server to delegate.\n\nIf --delegation is provided several times, the last set value is used.\n\nExample:\ncurl --delegation \"none\" https://example.com\n\nSee also -k, --insecure and --ssl.\n", "long": "--delegation", "arg": "" }, { "name": "--digest", "content": "(HTTP) Enables HTTP Digest authentication. This is an authentication scheme that pre‐\nvents the password from being sent over the wire in clear text. Use this in combina‐\ntion with the normal -u, --user option to set user name and password.\n\nProviding --digest multiple times has no extra effect. Disable it again with --no-di‐\ngest.\n\nExample:\ncurl -u name:password --digest https://example.com\n\nSee also -u, --user, --proxy-digest and --anyauth. This option is mutually exclusive\nto --basic and --ntlm and --negotiate.\n", "long": "--digest" }, { "name": "--disable-eprt", "content": "(FTP) Tell curl to disable the use of the EPRT and LPRT commands when doing active FTP\ntransfers. Curl normally first attempts to use EPRT before using PORT, but with this\noption, it uses PORT right away. EPRT is an extension to the original FTP protocol,\nand does not work on all servers, but enables more functionality in a better way than\nthe traditional PORT command.\n\n--eprt can be used to explicitly enable EPRT again and --no-eprt is an alias for\n--disable-eprt.\n\nIf the server is accessed using IPv6, this option has no effect as EPRT is necessary\nthen.\n\nDisabling EPRT only changes the active behavior. If you want to switch to passive mode\nyou need to not use -P, --ftp-port or force it with --ftp-pasv.\n\nProviding --disable-eprt multiple times has no extra effect. Disable it again with\n--no-disable-eprt.\n\nExample:\ncurl --disable-eprt ftp://example.com/\n\nSee also --disable-epsv and -P, --ftp-port.\n", "long": "--disable-eprt" }, { "name": "--disable-epsv", "content": "(FTP) Tell curl to disable the use of the EPSV command when doing passive FTP trans‐\nfers. Curl normally first attempts to use EPSV before PASV, but with this option, it\ndoes not try EPSV.\n\n--epsv can be used to explicitly enable EPSV again and --no-epsv is an alias for\n--disable-epsv.\n\nIf the server is an IPv6 host, this option has no effect as EPSV is necessary then.\n\nDisabling EPSV only changes the passive behavior. If you want to switch to active mode\nyou need to use -P, --ftp-port.\n\nProviding --disable-epsv multiple times has no extra effect. Disable it again with\n--no-disable-epsv.\n\nExample:\ncurl --disable-epsv ftp://example.com/\n\nSee also --disable-eprt and -P, --ftp-port.\n", "long": "--disable-epsv" }, { "name": "-q, --disable", "content": "If used as the first parameter on the command line, the curlrc config file is not read\nor used. See the -K, --config for details on the default config file search path.\n\nPrior to 7.50.0 curl supported the short option name q but not the long option name\ndisable.\n\nProviding -q, --disable multiple times has no extra effect. Disable it again with\n--no-disable.\n\nExample:\ncurl -q https://example.com\n\nSee also -K, --config.\n", "flag": "-q", "long": "--disable" }, { "name": "--disallow-username-in-url", "content": "(HTTP) This tells curl to exit if passed a URL containing a username. This is probably\nmost useful when the URL is being provided at runtime or similar.\n\nProviding --disallow-username-in-url multiple times has no extra effect. Disable it\nagain with --no-disallow-username-in-url.\n\nExample:\ncurl --disallow-username-in-url https://example.com\n\nSee also --proto. Added in 7.61.0.\n", "long": "--disallow-username-in-url" }, { "name": "--dns-interface ", "content": "(DNS) Tell curl to send outgoing DNS requests through . This option is a\ncounterpart to --interface (which does not affect DNS). The supplied string must be an\ninterface name (not an address).\n\nIf --dns-interface is provided several times, the last set value is used.\n\nExample:\ncurl --dns-interface eth0 https://example.com\n\nSee also --dns-ipv4-addr and --dns-ipv6-addr. --dns-interface requires that the under‐\nlying libcurl was built to support c-ares.\n", "long": "--dns-interface", "arg": "" }, { "name": "--dns-ipv4-addr
", "content": "(DNS) Tell curl to bind to a specific IP address when making IPv4 DNS requests, so\nthat the DNS requests originate from this address. The argument should be a single\nIPv4 address.\n\nIf --dns-ipv4-addr is provided several times, the last set value is used.\n\nExample:\ncurl --dns-ipv4-addr 10.1.2.3 https://example.com\n\nSee also --dns-interface and --dns-ipv6-addr. --dns-ipv4-addr requires that the under‐\nlying libcurl was built to support c-ares.\n", "long": "--dns-ipv4-addr", "arg": "
" }, { "name": "--dns-ipv6-addr
", "content": "(DNS) Tell curl to bind to a specific IP address when making IPv6 DNS requests, so\nthat the DNS requests originate from this address. The argument should be a single\nIPv6 address.\n\nIf --dns-ipv6-addr is provided several times, the last set value is used.\n\nExample:\ncurl --dns-ipv6-addr 2a04:4e42::561 https://example.com\n\nSee also --dns-interface and --dns-ipv4-addr. --dns-ipv6-addr requires that the under‐\nlying libcurl was built to support c-ares.\n", "long": "--dns-ipv6-addr", "arg": "
" }, { "name": "--dns-servers ", "content": "Set the list of DNS servers to be used instead of the system default. The list of IP\naddresses should be separated with commas. Port numbers may also optionally be given\nas : after each IP address.\n\nIf --dns-servers is provided several times, the last set value is used.\n\nExample:\ncurl --dns-servers 192.168.0.1,192.168.0.2 https://example.com\n\nSee also --dns-interface and --dns-ipv4-addr. --dns-servers requires that the underly‐\ning libcurl was built to support c-ares.\n", "long": "--dns-servers", "arg": "" }, { "name": "--doh-cert-status", "content": "Same as --cert-status but used for DoH (DNS-over-HTTPS).\n\nProviding --doh-cert-status multiple times has no extra effect. Disable it again with\n--no-doh-cert-status.\n\nExample:\ncurl --doh-cert-status --doh-url https://doh.example https://example.com\n\nSee also --doh-insecure. Added in 7.76.0.\n", "long": "--doh-cert-status" }, { "name": "--doh-insecure", "content": "Same as -k, --insecure but used for DoH (DNS-over-HTTPS).\n\nProviding --doh-insecure multiple times has no extra effect. Disable it again with\n--no-doh-insecure.\n\nExample:\ncurl --doh-insecure --doh-url https://doh.example https://example.com\n\nSee also --doh-url. Added in 7.76.0.\n", "long": "--doh-insecure" }, { "name": "--doh-url ", "content": "Specifies which DNS-over-HTTPS (DoH) server to use to resolve hostnames, instead of\nusing the default name resolver mechanism. The URL must be HTTPS.\n\nSome SSL options that you set for your transfer also applies to DoH since the name\nlookups take place over SSL. However, the certificate verification settings are not\ninherited but are controlled separately via --doh-insecure and --doh-cert-status.\n\nThis option is unset if an empty string \"\" is used as the URL. (Added in 7.85.0)\n\nIf --doh-url is provided several times, the last set value is used.\n\nExample:\ncurl --doh-url https://doh.example https://example.com\n\nSee also --doh-insecure. Added in 7.62.0.\n", "long": "--doh-url", "arg": "" }, { "name": "-D, --dump-header ", "content": "(HTTP FTP) Write the received protocol headers to the specified file. If no headers\nare received, the use of this option creates an empty file.\n\nWhen used in FTP, the FTP server response lines are considered being \"headers\" and\nthus are saved there.\n\nHaving multiple transfers in one set of operations (i.e. the URLs in one -:, --next\nclause), appends them to the same file, separated by a blank line.\n\nIf -D, --dump-header is provided several times, the last set value is used.\n\nExample:\ncurl --dump-header store.txt https://example.com\n\nSee also -o, --output.\n", "flag": "-D", "long": "--dump-header", "arg": "" }, { "name": "--egd-file ", "content": "(TLS) Deprecated option (added in 7.84.0). Prior to that it only had an effect on curl\nif built to use old versions of OpenSSL.\n\nSpecify the path name to the Entropy Gathering Daemon socket. The socket is used to\nseed the random engine for SSL connections.\n\nIf --egd-file is provided several times, the last set value is used.\n\nExample:\ncurl --egd-file /random/here https://example.com\n\nSee also --random-file.\n", "long": "--egd-file", "arg": "" }, { "name": "--engine ", "content": "(TLS) Select the OpenSSL crypto engine to use for cipher operations. Use --engine list\nto print a list of build-time supported engines. Note that not all (and possibly none)\nof the engines may be available at runtime.\n\nIf --engine is provided several times, the last set value is used.\n\nExample:\ncurl --engine flavor https://example.com\n\nSee also --ciphers and --curves.\n", "long": "--engine", "arg": "" }, { "name": "--etag-compare ", "content": "(HTTP) This option makes a conditional HTTP request for the specific ETag read from\nthe given file by sending a custom If-None-Match header using the stored ETag.\n\nFor correct results, make sure that the specified file contains only a single line\nwith the desired ETag. An empty file is parsed as an empty ETag.\n\nUse the option --etag-save to first save the ETag from a response, and then use this\noption to compare against the saved ETag in a subsequent request.\n\nIf --etag-compare is provided several times, the last set value is used.\n\nExample:\ncurl --etag-compare etag.txt https://example.com\n\nSee also --etag-save and -z, --time-cond. Added in 7.68.0.\n", "long": "--etag-compare", "arg": "" }, { "name": "--etag-save ", "content": "(HTTP) This option saves an HTTP ETag to the specified file. An ETag is a caching re‐\nlated header, usually returned in a response.\n\nIf no ETag is sent by the server, an empty file is created.\n\nIf --etag-save is provided several times, the last set value is used.\n\nExample:\ncurl --etag-save storetag.txt https://example.com\n\nSee also --etag-compare. Added in 7.68.0.\n", "long": "--etag-save", "arg": "" }, { "name": "--expect100-timeout ", "content": "(HTTP) Maximum time in seconds that you allow curl to wait for a 100-continue response\nwhen curl emits an Expects: 100-continue header in its request. By default curl waits\none second. This option accepts decimal values! When curl stops waiting, it continues\nas if the response has been received.\n\nThe decimal value needs to provided using a dot (.) as decimal separator - not the lo‐\ncal version even if it might be using another separator.\n\nIf --expect100-timeout is provided several times, the last set value is used.\n\nExample:\ncurl --expect100-timeout 2.5 -T file https://example.com\n\nSee also --connect-timeout.\n", "long": "--expect100-timeout", "arg": "" }, { "name": "--fail-early", "content": "Fail and exit on the first detected transfer error.\n\nWhen curl is used to do multiple transfers on the command line, it attempts to operate\non each given URL, one by one. By default, it ignores errors if there are more URLs\ngiven and the last URL's success determines the error code curl returns. So early\nfailures are \"hidden\" by subsequent successful transfers.\n\nUsing this option, curl instead returns an error on the first transfer that fails, in‐\ndependent of the amount of URLs that are given on the command line. This way, no\ntransfer failures go undetected by scripts and similar.\n\nThis option does not imply -f, --fail, which causes transfers to fail due to the\nserver's HTTP status code. You can combine the two options, however note -f, --fail is\nnot global and is therefore contained by -:, --next.\n\nThis option is global and does not need to be specified for each use of --next.\n\nProviding --fail-early multiple times has no extra effect. Disable it again with\n--no-fail-early.\n\nExample:\ncurl --fail-early https://example.com https://two.example\n\nSee also -f, --fail and --fail-with-body. Added in 7.52.0.\n", "long": "--fail-early" }, { "name": "--fail-with-body", "content": "(HTTP) Return an error on server errors where the HTTP response code is 400 or\ngreater). In normal cases when an HTTP server fails to deliver a document, it returns\nan HTML document stating so (which often also describes why and more). This flag al‐\nlows curl to output and save that content but also to return error 22.\n\nThis is an alternative option to -f, --fail which makes curl fail for the same circum‐\nstances but without saving the content.\n\nProviding --fail-with-body multiple times has no extra effect. Disable it again with\n--no-fail-with-body.\n\nExample:\ncurl --fail-with-body https://example.com\n\nSee also -f, --fail and --fail-early. This option is mutually exclusive to -f, --fail.\nAdded in 7.76.0.\n", "long": "--fail-with-body" }, { "name": "-f, --fail", "content": "(HTTP) Fail fast with no output at all on server errors. This is useful to enable\nscripts and users to better deal with failed attempts. In normal cases when an HTTP\nserver fails to deliver a document, it returns an HTML document stating so (which of‐\nten also describes why and more). This flag prevents curl from outputting that and re‐\nturn error 22.\n\nThis method is not fail-safe and there are occasions where non-successful response\ncodes slip through, especially when authentication is involved (response codes 401 and\n407).\n\nProviding -f, --fail multiple times has no extra effect. Disable it again with\n--no-fail.\n\nExample:\ncurl --fail https://example.com\n\nSee also --fail-with-body and --fail-early. This option is mutually exclusive to\n--fail-with-body.\n", "flag": "-f", "long": "--fail" }, { "name": "--false-start", "content": "(TLS) Tells curl to use false start during the TLS handshake. False start is a mode\nwhere a TLS client starts sending application data before verifying the server's Fin‐\nished message, thus saving a round trip when performing a full handshake.\n\nThis is currently only implemented in the Secure Transport (on iOS 7.0 or later, or OS\nX 10.9 or later) backend.\n\nProviding --false-start multiple times has no extra effect. Disable it again with\n--no-false-start.\n\nExample:\ncurl --false-start https://example.com\n\nSee also --tcp-fastopen.\n", "long": "--false-start" }, { "name": "--form-escape", "content": "(HTTP) Tells curl to pass on names of multipart form fields and files using back‐\nslash-escaping instead of percent-encoding.\n\nIf --form-escape is provided several times, the last set value is used.\n\nExample:\ncurl --form-escape -F 'field\\name=curl' -F 'file=@load\"this' https://example.com\n\nSee also -F, --form. Added in 7.81.0.\n", "long": "--form-escape" }, { "name": "--form-string ", "content": "(HTTP SMTP IMAP) Similar to -F, --form except that the value string for the named pa‐\nrameter is used literally. Leading '@' and '<' characters, and the ';type=' string in\nthe value have no special meaning. Use this in preference to -F, --form if there is\nany possibility that the string value may accidentally trigger the '@' or '<' features\nof -F, --form.\n\n--form-string can be used several times in a command line\n\nExample:\ncurl --form-string \"data\" https://example.com\n\nSee also -F, --form.\n", "long": "--form-string", "arg": "" }, { "name": "-F, --form ", "content": "(HTTP SMTP IMAP) For HTTP protocol family, this lets curl emulate a filled-in form in\nwhich a user has pressed the submit button. This causes curl to POST data using the\nContent-Type multipart/form-data according to RFC 2388.\n\nFor SMTP and IMAP protocols, this is the means to compose a multipart mail message to\ntransmit.\n\nThis enables uploading of binary files etc. To force the 'content' part to be a file,\nprefix the file name with an @ sign. To just get the content part from a file, prefix\nthe file name with the symbol <. The difference between @ and < is then that @ makes a\nfile get attached in the post as a file upload, while the < makes a text field and\njust get the contents for that text field from a file.\n\nTell curl to read content from stdin instead of a file by using - as filename. This\ngoes for both @ and < constructs. When stdin is used, the contents is buffered in mem‐\nory first by curl to determine its size and allow a possible resend. Defining a part's\ndata from a named non-regular file (such as a named pipe or similar) is not subject to\nbuffering and is instead read at transmission time; since the full size is unknown be‐\nfore the transfer starts, such data is sent as chunks by HTTP and rejected by IMAP.\n\nExample: send an image to an HTTP server, where 'profile' is the name of the\nform-field to which the file portrait.jpg is the input:\n\ncurl -F profile=@portrait.jpg https://example.com/upload.cgi\n\nExample: send your name and shoe size in two text fields to the server:\n\ncurl -F name=John -F shoesize=11 https://example.com/\n\nExample: send your essay in a text field to the server. Send it as a plain text field,\nbut get the contents for it from a local file:\n\ncurl -F \"story=HTML message;type=text/html' \\\n-F '=)' -F '=@textfile.txt' ... smtp://example.com\n\nData can be encoded for transfer using encoder=. Available encodings are binary and\n8bit that do nothing else than adding the corresponding Content-Transfer-Encoding\nheader, 7bit that only rejects 8-bit characters with a transfer error, quoted-print‐\nable and base64 that encodes data according to the corresponding schemes, limiting\nlines length to 76 characters.\n\nExample: send multipart mail with a quoted-printable text message and a base64 at‐\ntached file:\n\ncurl -F '=text message;encoder=quoted-printable' \\\n-F '=@localfile;encoder=base64' ... smtp://example.com\n\nSee further examples and details in the MANUAL.\n\n-F, --form can be used several times in a command line\n\nExample:\ncurl --form \"name=curl\" --form \"file=@loadthis\" https://example.com\n\nSee also -d, --data, --form-string and --form-escape. This option is mutually exclu‐\nsive to -d, --data and -I, --head and -T, --upload-file.\n", "flag": "-F", "long": "--form", "arg": "" }, { "name": "--ftp-account ", "content": "(FTP) When an FTP server asks for \"account data\" after user name and password has been\nprovided, this data is sent off using the ACCT command.\n\nIf --ftp-account is provided several times, the last set value is used.\n\nExample:\ncurl --ftp-account \"mr.robot\" ftp://example.com/\n\nSee also -u, --user.\n", "long": "--ftp-account", "arg": "" }, { "name": "--ftp-alternative-to-user ", "content": "(FTP) If authenticating with the USER and PASS commands fails, send this command.\nWhen connecting to Tumbleweed's Secure Transport server over FTPS using a client cer‐\ntificate, using \"SITE AUTH\" tells the server to retrieve the username from the cer‐\ntificate.\n\nIf --ftp-alternative-to-user is provided several times, the last set value is used.\n\nExample:\ncurl --ftp-alternative-to-user \"U53r\" ftp://example.com\n\nSee also --ftp-account and -u, --user.\n", "long": "--ftp-alternative-to-user", "arg": "" }, { "name": "--ftp-create-dirs", "content": "(FTP SFTP) When an FTP or SFTP URL/operation uses a path that does not currently exist\non the server, the standard behavior of curl is to fail. Using this option, curl in‐\nstead attempts to create missing directories.\n\nProviding --ftp-create-dirs multiple times has no extra effect. Disable it again with\n--no-ftp-create-dirs.\n\nExample:\ncurl --ftp-create-dirs -T file ftp://example.com/remote/path/file\n\nSee also --create-dirs.\n", "long": "--ftp-create-dirs" }, { "name": "--ftp-method ", "content": "(FTP) Control what method curl should use to reach a file on an FTP(S) server. The\nmethod argument should be one of the following alternatives:\n\nmulticwd\ncurl does a single CWD operation for each path part in the given URL. For deep\nhierarchies this means many commands. This is how RFC 1738 says it should be\ndone. This is the default but the slowest behavior.\n\nnocwd curl does no CWD at all. curl does SIZE, RETR, STOR etc and give a full path to\nthe server for all these commands. This is the fastest behavior.\n\nsinglecwd\ncurl does one CWD with the full target directory and then operates on the file\n\"normally\" (like in the multicwd case). This is somewhat more standards compli‐\nant than 'nocwd' but without the full penalty of 'multicwd'.\n\nIf --ftp-method is provided several times, the last set value is used.\n\nExamples:\ncurl --ftp-method multicwd ftp://example.com/dir1/dir2/file\ncurl --ftp-method nocwd ftp://example.com/dir1/dir2/file\ncurl --ftp-method singlecwd ftp://example.com/dir1/dir2/file\n\nSee also -l, --list-only.\n", "long": "--ftp-method", "arg": "" }, { "name": "--ftp-pasv", "content": "(FTP) Use passive mode for the data connection. Passive is the internal default behav‐\nior, but using this option can be used to override a previous -P, --ftp-port option.\n\nReversing an enforced passive really is not doable but you must then instead enforce\nthe correct -P, --ftp-port again.\n\nPassive mode means that curl tries the EPSV command first and then PASV, unless --dis‐\nable-epsv is used.\n\nProviding --ftp-pasv multiple times has no extra effect. Disable it again with\n--no-ftp-pasv.\n\nExample:\ncurl --ftp-pasv ftp://example.com/\n\nSee also --disable-epsv.\n", "long": "--ftp-pasv" }, { "name": "-P, --ftp-port
", "content": "(FTP) Reverses the default initiator/listener roles when connecting with FTP. This op‐\ntion makes curl use active mode. curl then tells the server to connect back to the\nclient's specified address and port, while passive mode asks the server to setup an IP\naddress and port for it to connect to.
should be one of:\n\ninterface\ne.g. \"eth0\" to specify which interface's IP address you want to use (Unix only)\n\nIP address\ne.g. \"192.168.10.1\" to specify the exact IP address\n\nhost name\ne.g. \"my.host.domain\" to specify the machine\n\n- make curl pick the same IP address that is already used for the control connec‐\ntion\n\nDisable the use of PORT with --ftp-pasv. Disable the attempt to use the EPRT command\ninstead of PORT by using --disable-eprt. EPRT is really PORT++.\n\nYou can also append \":[start]-[end]\" to the right of the address, to tell curl what\nTCP port range to use. That means you specify a port range, from a lower to a higher\nnumber. A single number works as well, but do note that it increases the risk of fail‐\nure since the port may not be available.\n\n\nIf -P, --ftp-port is provided several times, the last set value is used.\n\nExamples:\ncurl -P - ftp:/example.com\ncurl -P eth0 ftp:/example.com\ncurl -P 192.168.0.2 ftp:/example.com\n\nSee also --ftp-pasv and --disable-eprt.\n", "flag": "-P", "long": "--ftp-port", "arg": "
" }, { "name": "--ftp-pret", "content": "(FTP) Tell curl to send a PRET command before PASV (and EPSV). Certain FTP servers,\nmainly drftpd, require this non-standard command for directory listings as well as up\nand downloads in PASV mode.\n\nProviding --ftp-pret multiple times has no extra effect. Disable it again with\n--no-ftp-pret.\n\nExample:\ncurl --ftp-pret ftp://example.com/\n\nSee also -P, --ftp-port and --ftp-pasv.\n", "long": "--ftp-pret" }, { "name": "--ftp-skip-pasv-ip", "content": "(FTP) Tell curl to not use the IP address the server suggests in its response to\ncurl's PASV command when curl connects the data connection. Instead curl reuses the\nsame IP address it already uses for the control connection.\n\nThis option is enabled by default (added in 7.74.0).\n\nThis option has no effect if PORT, EPRT or EPSV is used instead of PASV.\n\nProviding --ftp-skip-pasv-ip multiple times has no extra effect. Disable it again\nwith --no-ftp-skip-pasv-ip.\n\nExample:\ncurl --ftp-skip-pasv-ip ftp://example.com/\n\nSee also --ftp-pasv.\n", "long": "--ftp-skip-pasv-ip" }, { "name": "--ftp-ssl-ccc-mode ", "content": "(FTP) Sets the CCC mode. The passive mode does not initiate the shutdown, but instead\nwaits for the server to do it, and does not reply to the shutdown from the server. The\nactive mode initiates the shutdown and waits for a reply from the server.\n\nProviding --ftp-ssl-ccc-mode multiple times has no extra effect. Disable it again\nwith --no-ftp-ssl-ccc-mode.\n\nExample:\ncurl --ftp-ssl-ccc-mode active --ftp-ssl-ccc ftps://example.com/\n\nSee also --ftp-ssl-ccc.\n", "long": "--ftp-ssl-ccc-mode", "arg": "" }, { "name": "--ftp-ssl-ccc", "content": "(FTP) Use CCC (Clear Command Channel) Shuts down the SSL/TLS layer after authenticat‐\ning. The rest of the control channel communication is be unencrypted. This allows NAT\nrouters to follow the FTP transaction. The default mode is passive.\n\nProviding --ftp-ssl-ccc multiple times has no extra effect. Disable it again with\n--no-ftp-ssl-ccc.\n\nExample:\ncurl --ftp-ssl-ccc ftps://example.com/\n\nSee also --ssl and --ftp-ssl-ccc-mode.\n", "long": "--ftp-ssl-ccc" }, { "name": "--ftp-ssl-control", "content": "(FTP) Require SSL/TLS for the FTP login, clear for transfer. Allows secure authenti‐\ncation, but non-encrypted data transfers for efficiency. Fails the transfer if the\nserver does not support SSL/TLS.\n\nProviding --ftp-ssl-control multiple times has no extra effect. Disable it again with\n--no-ftp-ssl-control.\n\nExample:\ncurl --ftp-ssl-control ftp://example.com\n\nSee also --ssl.\n", "long": "--ftp-ssl-control" }, { "name": "-G, --get", "content": "When used, this option makes all data specified with -d, --data, --data-binary or\n--data-urlencode to be used in an HTTP GET request instead of the POST request that\notherwise would be used. The data is appended to the URL with a '?' separator.\n\nIf used in combination with -I, --head, the POST data is instead appended to the URL\nwith a HEAD request.\n\nProviding -G, --get multiple times has no extra effect. Disable it again with\n--no-get.\n\nExamples:\ncurl --get https://example.com\ncurl --get -d \"tool=curl\" -d \"age=old\" https://example.com\ncurl --get -I -d \"tool=curl\" https://example.com\n\nSee also -d, --data and -X, --request.\n", "flag": "-G", "long": "--get" }, { "name": "-g, --globoff", "content": "This option switches off the \"URL globbing parser\". When you set this option, you can\nspecify URLs that contain the letters {}[] without having curl itself interpret them.\nNote that these letters are not normal legal URL contents but they should be encoded\naccording to the URI standard.\n\nProviding -g, --globoff multiple times has no extra effect. Disable it again with\n--no-globoff.\n\nExample:\ncurl -g \"https://example.com/{[]}}}}\"\n\nSee also -K, --config and -q, --disable.\n", "flag": "-g", "long": "--globoff" }, { "name": "--happy-eyeballs-timeout-ms ", "content": "Happy Eyeballs is an algorithm that attempts to connect to both IPv4 and IPv6 ad‐\ndresses for dual-stack hosts, giving IPv6 a head-start of the specified number of mil‐\nliseconds. If the IPv6 address cannot be connected to within that time, then a connec‐\ntion attempt is made to the IPv4 address in parallel. The first connection to be es‐\ntablished is the one that is used.\n\nThe range of suggested useful values is limited. Happy Eyeballs RFC 6555 says \"It is\nRECOMMENDED that connection attempts be paced 150-250 ms apart to balance human fac‐\ntors against network load.\" libcurl currently defaults to 200 ms. Firefox and Chrome\ncurrently default to 300 ms.\n\nIf --happy-eyeballs-timeout-ms is provided several times, the last set value is used.\n\nExample:\ncurl --happy-eyeballs-timeout-ms 500 https://example.com\n\nSee also -m, --max-time and --connect-timeout. Added in 7.59.0.\n", "long": "--happy-eyeballs-timeout-ms", "arg": "" }, { "name": "--haproxy-clientip", "content": "(HTTP) Sets a client IP in HAProxy PROXY protocol v1 header at the beginning of the\nconnection.\n\nFor valid requests, IPv4 addresses must be indicated as a series of exactly 4 integers\nin the range [0..255] inclusive written in decimal representation separated by exactly\none dot between each other. Heading zeroes are not permitted in front of numbers in\norder to avoid any possible confusion with octal numbers. IPv6 addresses must be indi‐\ncated as series of 4 hexadecimal digits (upper or lower case) delimited by colons be‐\ntween each other, with the acceptance of one double colon sequence to replace the\nlargest acceptable range of consecutive zeroes. The total number of decoded bits must\nexactly be 128.\n\nOtherwise, any string can be accepted for the client IP and get sent.\n\nIt replaces --haproxy-protocol if used, it is not necessary to specify both flags.\n\nThis option is primarily useful when sending test requests to verify a service is\nworking as intended.\n\nIf --haproxy-clientip is provided several times, the last set value is used.\n\nExample:\ncurl --haproxy-clientip $IP\n\nSee also -x, --proxy. Added in 8.2.0.\n", "long": "--haproxy-clientip" }, { "name": "--haproxy-protocol", "content": "(HTTP) Send a HAProxy PROXY protocol v1 header at the beginning of the connection.\nThis is used by some load balancers and reverse proxies to indicate the client's true\nIP address and port.\n\nThis option is primarily useful when sending test requests to a service that expects\nthis header.\n\nProviding --haproxy-protocol multiple times has no extra effect. Disable it again\nwith --no-haproxy-protocol.\n\nExample:\ncurl --haproxy-protocol https://example.com\n\nSee also -x, --proxy. Added in 7.60.0.\n", "long": "--haproxy-protocol" }, { "name": "-I, --head", "content": "(HTTP FTP FILE) Fetch the headers only! HTTP-servers feature the command HEAD which\nthis uses to get nothing but the header of a document. When used on an FTP or FILE\nfile, curl displays the file size and last modification time only.\n\nProviding -I, --head multiple times has no extra effect. Disable it again with\n--no-head.\n\nExample:\ncurl -I https://example.com\n\nSee also -G, --get, -v, --verbose and --trace-ascii.\n", "flag": "-I", "long": "--head" }, { "name": "-H, --header
", "content": "(HTTP IMAP SMTP) Extra header to include in information sent. When used within an HTTP\nrequest, it is added to the regular request headers.\n\nFor an IMAP or SMTP MIME uploaded mail built with -F, --form options, it is prepended\nto the resulting MIME document, effectively including it at the mail global level. It\ndoes not affect raw uploaded mails (Added in 7.56.0).\n\nYou may specify any number of extra headers. Note that if you should add a custom\nheader that has the same name as one of the internal ones curl would use, your exter‐\nnally set header is used instead of the internal one. This allows you to make even\ntrickier stuff than curl would normally do. You should not replace internally set\nheaders without knowing perfectly well what you are doing. Remove an internal header\nby giving a replacement without content on the right side of the colon, as in: -H\n\"Host:\". If you send the custom header with no-value then its header must be termi‐\nnated with a semicolon, such as -H \"X-Custom-Header;\" to send \"X-Custom-Header:\".\n\ncurl makes sure that each header you add/replace is sent with the proper end-of-line\nmarker, you should thus not add that as a part of the header content: do not add new‐\nlines or carriage returns, they only mess things up for you. curl passes on the verba‐\ntim string you give it without any filter or other safe guards. That includes white\nspace and control characters.\n\nThis option can take an argument in @filename style, which then adds a header for each\nline in the input file. Using @- makes curl read the header file from stdin. Added in\n7.55.0.\n\nPlease note that most anti-spam utilities check the presence and value of several MIME\nmail headers: these are \"From:\", \"To:\", \"Date:\" and \"Subject:\" among others and should\nbe added with this option.\n\nYou need --proxy-header to send custom headers intended for an HTTP proxy. Added in\n7.37.0.\n\nPassing on a \"Transfer-Encoding: chunked\" header when doing an HTTP request with a re‐\nquest body, makes curl send the data using chunked encoding.\n\nWARNING: headers set with this option are set in all HTTP requests - even after redi‐\nrects are followed, like when told with -L, --location. This can lead to the header\nbeing sent to other hosts than the original host, so sensitive headers should be used\nwith caution combined with following redirects.\n\n-H, --header can be used several times in a command line\n\nExamples:\ncurl -H \"X-First-Name: Joe\" https://example.com\ncurl -H \"User-Agent: yes-please/2000\" https://example.com\ncurl -H \"Host:\" https://example.com\ncurl -H @headers.txt https://example.com\n\nSee also -A, --user-agent and -e, --referer.\n", "flag": "-H", "long": "--header", "arg": "
" }, { "name": "-h, --help ", "content": "Usage help. This lists all curl command line options within the given category.\n\nIf no argument is provided, curl displays only the most important command line argu‐\nments.\n\nFor category all, curl displays help for all options.\n\nIf category is specified, curl displays all available help categories.\n\nExample:\ncurl --help all\n\nSee also -v, --verbose.\n", "flag": "-h", "long": "--help", "arg": "" }, { "name": "--hostpubmd5 ", "content": "(SFTP SCP) Pass a string containing 32 hexadecimal digits. The string should be the\n128 bit MD5 checksum of the remote host's public key, curl refuses the connection with\nthe host unless the md5sums match.\n\nIf --hostpubmd5 is provided several times, the last set value is used.\n\nExample:\ncurl --hostpubmd5 e5c1c49020640a5ab0f2034854c321a8 sftp://example.com/\n\nSee also --hostpubsha256.\n", "long": "--hostpubmd5", "arg": "" }, { "name": "--hostpubsha256 ", "content": "(SFTP SCP) Pass a string containing a Base64-encoded SHA256 hash of the remote host's\npublic key. Curl refuses the connection with the host unless the hashes match.\n\nThis feature requires libcurl to be built with libssh2 and does not work with other\nSSH backends.\n\nIf --hostpubsha256 is provided several times, the last set value is used.\n\nExample:\ncurl --hostpubsha256 NDVkMTQxMGQ1ODdmMjQ3MjczYjAyOTY5MmRkMjVmNDQ= sftp://example.com/\n\nSee also --hostpubmd5. Added in 7.80.0.\n", "long": "--hostpubsha256", "arg": "" }, { "name": "--hsts ", "content": "(HTTPS) This option enables HSTS for the transfer. If the file name points to an ex‐\nisting HSTS cache file, that is used. After a completed transfer, the cache is saved\nto the file name again if it has been modified.\n\nIf curl is told to use HTTP:// for a transfer involving a host name that exists in the\nHSTS cache, it upgrades the transfer to use HTTPS. Each HSTS cache entry has an indi‐\nvidual life time after which the upgrade is no longer performed.\n\nSpecify a \"\" file name (zero length) to avoid loading/saving and make curl just handle\nHSTS in memory.\n\nIf this option is used several times, curl loads contents from all the files but the\nlast one is used for saving.\n\n--hsts can be used several times in a command line\n\nExample:\ncurl --hsts cache.txt https://example.com\n\nSee also --proto. Added in 7.74.0.\n\n--http0.9\n(HTTP) Tells curl to be fine with HTTP version 0.9 response.\n\nHTTP/0.9 is a response without headers and therefore you can also connect with this to\nnon-HTTP servers and still get a response since curl simply transparently downgrades -\nif allowed.\n\nHTTP/0.9 is disabled by default (added in 7.66.0)\n\nProviding --http0.9 multiple times has no extra effect. Disable it again with\n--no-http0.9.\n\nExample:\ncurl --http0.9 https://example.com\n\nSee also --http1.1, --http2 and --http3. Added in 7.64.0.\n\n-0, --http1.0\n(HTTP) Tells curl to use HTTP version 1.0 instead of using its internally preferred\nHTTP version.\n\nProviding -0, --http1.0 multiple times has no extra effect.\n\nExample:\ncurl --http1.0 https://example.com\n\nSee also --http0.9 and --http1.1. This option is mutually exclusive to --http1.1 and\n--http2 and --http2-prior-knowledge and --http3.\n\n--http1.1\n(HTTP) Tells curl to use HTTP version 1.1.\n\nProviding --http1.1 multiple times has no extra effect.\n\nExample:\ncurl --http1.1 https://example.com\n\nSee also -0, --http1.0 and --http0.9. This option is mutually exclusive to -0,\n--http1.0 and --http2 and --http2-prior-knowledge and --http3.\n", "long": "--hsts" }, { "name": "--http2-prior-knowledge", "content": "(HTTP) Tells curl to issue its non-TLS HTTP requests using HTTP/2 without HTTP/1.1 Up‐\ngrade. It requires prior knowledge that the server supports HTTP/2 straight away.\nHTTPS requests still do HTTP/2 the standard way with negotiated protocol version in\nthe TLS handshake.\n\nProviding --http2-prior-knowledge multiple times has no extra effect. Disable it\nagain with --no-http2-prior-knowledge.\n\nExample:\ncurl --http2-prior-knowledge https://example.com\n\nSee also --http2 and --http3. --http2-prior-knowledge requires that the underlying\nlibcurl was built to support HTTP/2. This option is mutually exclusive to --http1.1\nand -0, --http1.0 and --http2 and --http3.\n", "long": "--http2-prior-knowledge" }, { "name": "--http2", "content": "(HTTP) Tells curl to use HTTP version 2.\n\nFor HTTPS, this means curl negotiates HTTP/2 in the TLS handshake. curl does this by\ndefault.\n\nFor HTTP, this means curl attempts to upgrade the request to HTTP/2 using the Upgrade:\nrequest header.\n\nWhen curl uses HTTP/2 over HTTPS, it does not itself insist on TLS 1.2 or higher even\nthough that is required by the specification. A user can add this version requirement\nwith --tlsv1.2.\n\nProviding --http2 multiple times has no extra effect.\n\nExample:\ncurl --http2 https://example.com\n\nSee also --http1.1, --http3 and --no-alpn. --http2 requires that the underlying\nlibcurl was built to support HTTP/2. This option is mutually exclusive to --http1.1\nand -0, --http1.0 and --http2-prior-knowledge and --http3.\n", "long": "--http2" }, { "name": "--http3-only", "content": "(HTTP) WARNING: this option is experimental. Do not use in production.\n\nInstructs curl to use HTTP/3 to the host in the URL, with no fallback to earlier HTTP\nversions. HTTP/3 can only be used for HTTPS and not for HTTP URLs. For HTTP, this op‐\ntion triggers an error.\n\nThis option allows a user to avoid using the Alt-Svc method of upgrading to HTTP/3\nwhen you know that the target speaks HTTP/3 on the given host and port.\n\nThis option makes curl fail if a QUIC connection cannot be established, it does not\nattempt any other HTTP versions on its own. Use --http3 for similar functionality with\na fallback.\n\nProviding --http3-only multiple times has no extra effect.\n\nExample:\ncurl --http3-only https://example.com\n\nSee also --http1.1, --http2 and --http3. --http3-only requires that the underlying\nlibcurl was built to support HTTP/3. This option is mutually exclusive to --http1.1\nand -0, --http1.0 and --http2 and --http2-prior-knowledge and --http3. Added in\n7.88.0.\n", "long": "--http3-only" }, { "name": "--http3", "content": "(HTTP) WARNING: this option is experimental. Do not use in production.\n\nTells curl to try HTTP/3 to the host in the URL, but fallback to earlier HTTP versions\nif the HTTP/3 connection establishment fails. HTTP/3 is only available for HTTPS and\nnot for HTTP URLs.\n\nThis option allows a user to avoid using the Alt-Svc method of upgrading to HTTP/3\nwhen you know that the target speaks HTTP/3 on the given host and port.\n\nWhen asked to use HTTP/3, curl issues a separate attempt to use older HTTP versions\nwith a slight delay, so if the HTTP/3 transfer fails or is slow, curl still tries to\nproceed with an older HTTP version.\n\nUse --http3-only for similar functionality without a fallback.\n\nProviding --http3 multiple times has no extra effect.\n\nExample:\ncurl --http3 https://example.com\n\nSee also --http1.1 and --http2. --http3 requires that the underlying libcurl was built\nto support HTTP/3. This option is mutually exclusive to --http1.1 and -0, --http1.0\nand --http2 and --http2-prior-knowledge and --http3-only. Added in 7.66.0.\n", "long": "--http3" }, { "name": "--ignore-content-length", "content": "(FTP HTTP) For HTTP, Ignore the Content-Length header. This is particularly useful for\nservers running Apache 1.x, which reports incorrect Content-Length for files larger\nthan 2 gigabytes.\n\nFor FTP, this makes curl skip the SIZE command to figure out the size before download‐\ning a file.\n\nThis option does not work for HTTP if libcurl was built to use hyper.\n\nProviding --ignore-content-length multiple times has no extra effect. Disable it\nagain with --no-ignore-content-length.\n\nExample:\ncurl --ignore-content-length https://example.com\n\nSee also --ftp-skip-pasv-ip.\n", "long": "--ignore-content-length" }, { "name": "-i, --include", "content": "Include the HTTP response headers in the output. The HTTP response headers can include\nthings like server name, cookies, date of the document, HTTP version and more...\n\nTo view the request headers, consider the -v, --verbose option.\n\nPrior to 7.75.0 curl did not print the headers if -f, --fail was used in combination\nwith this option and there was error reported by server.\n\nProviding -i, --include multiple times has no extra effect. Disable it again with\n--no-include.\n\nExample:\ncurl -i https://example.com\n\nSee also -v, --verbose.\n", "flag": "-i", "long": "--include" }, { "name": "-k, --insecure", "content": "(TLS SFTP SCP) By default, every secure connection curl makes is verified to be secure\nbefore the transfer takes place. This option makes curl skip the verification step and\nproceed without checking.\n\nWhen this option is not used for protocols using TLS, curl verifies the server's TLS\ncertificate before it continues: that the certificate contains the right name which\nmatches the host name used in the URL and that the certificate has been signed by a CA\ncertificate present in the cert store. See this online resource for further details:\nhttps://curl.se/docs/sslcerts.html\n\nFor SFTP and SCP, this option makes curl skip the knownhosts verification.\nknownhosts is a file normally stored in the user's home directory in the \".ssh\" sub‐\ndirectory, which contains host names and their public keys.\n\nWARNING: using this option makes the transfer insecure.\n\nWhen curl uses secure protocols it trusts responses and allows for example HSTS and\nAlt-Svc information to be stored and used subsequently. Using -k, --insecure can make\ncurl trust and use such information from malicious servers.\n\nProviding -k, --insecure multiple times has no extra effect. Disable it again with\n--no-insecure.\n\nExample:\ncurl --insecure https://example.com\n\nSee also --proxy-insecure, --cacert and --capath.\n", "flag": "-k", "long": "--insecure" }, { "name": "--interface ", "content": "Perform an operation using a specified interface. You can enter interface name, IP ad‐\ndress or host name. An example could look like:\n\ncurl --interface eth0:1 https://www.example.com/\n\nOn Linux it can be used to specify a VRF, but the binary needs to either have\nCAPNETRAW or to be run as root. More information about Linux VRF: https://www.ker‐\nnel.org/doc/Documentation/networking/vrf.txt\n\nIf --interface is provided several times, the last set value is used.\n\nExample:\ncurl --interface eth0 https://example.com\n\nSee also --dns-interface.\n", "long": "--interface", "arg": "" }, { "name": "--ipfs-gateway ", "content": "Specify which gateway to use for IPFS and IPNS URLs. Not specifying this will instead\nmake curl check if the IPFSGATEWAY environment variable is set, or if a ~/.ipfs/gate‐\nway file holding the gateway URL exists.\n\nIf you run a local IPFS node, this gateway is by default available under http://local‐\nhost:8080. A full example URL would look like:\n\ncurl --ipfs-gateway http://localhost:8080 ipfs://bafybeigagd5nmnn2iys2f3doro7ydrevyr2mzarwidgadawmamiteydbzi\n\nThere are many public IPFS gateways. See for example:\n\nhttps://ipfs.github.io/public-gateway-checker/\n\nWARNING: If you opt to go for a remote gateway you should be aware that you completely\ntrust the gateway. This is fine in local gateways as you host it yourself. With remote\ngateways there could potentially be a malicious actor returning you data that does not\nmatch the request you made, inspect or even interfere with the request. You will not\nnotice this when using curl. A mitigation could be to go for a \"trustless\" gateway.\nThis means you locally verify that the data. Consult the docs page on trusted vs\ntrustless: https://docs.ipfs.tech/reference/http/gateway/#trusted-vs-trustless\n\nIf --ipfs-gateway is provided several times, the last set value is used.\n\nExample:\ncurl --ipfs-gateway https://example.com ipfs://\n\nSee also -h, --help and -M, --manual. Added in 8.4.0.\n\n-4, --ipv4\nThis option tells curl to use IPv4 addresses only when resolving host names, and not\nfor example try IPv6.\n\nProviding -4, --ipv4 multiple times has no extra effect.\n\nExample:\ncurl --ipv4 https://example.com\n\nSee also --http1.1 and --http2. This option is mutually exclusive to -6, --ipv6.\n\n-6, --ipv6\nThis option tells curl to use IPv6 addresses only when resolving host names, and not\nfor example try IPv4.\n\nProviding -6, --ipv6 multiple times has no extra effect.\n\nExample:\ncurl --ipv6 https://example.com\n\nSee also --http1.1 and --http2. This option is mutually exclusive to -4, --ipv4.\n", "long": "--ipfs-gateway", "arg": "" }, { "name": "--json ", "content": "(HTTP) Sends the specified JSON data in a POST request to the HTTP server. --json\nworks as a shortcut for passing on these three options:\n\n--data [arg]\n--header \"Content-Type: application/json\"\n--header \"Accept: application/json\"\n\nThere is no verification that the passed in data is actual JSON or that the syntax is\ncorrect.\n\nIf you start the data with the letter @, the rest should be a file name to read the\ndata from, or a single dash (-) if you want curl to read the data from stdin. Posting\ndata from a file named 'foobar' would thus be done with --json @foobar and to instead\nread the data from stdin, use --json @-.\n\nIf this option is used more than once on the same command line, the additional data\npieces are concatenated to the previous before sending.\n\nThe headers this option sets can be overridden with -H, --header as usual.\n\n--json can be used several times in a command line\n\nExamples:\ncurl --json '{ \"drink\": \"coffe\" }' https://example.com\ncurl --json '{ \"drink\":' --json ' \"coffe\" }' https://example.com\ncurl --json @prepared https://example.com\ncurl --json @- https://example.com < json.txt\n\nSee also --data-binary and --data-raw. This option is mutually exclusive to -F, --form\nand -I, --head and -T, --upload-file. Added in 7.82.0.\n", "long": "--json", "arg": "" }, { "name": "-j, --junk-session-cookies", "content": "(HTTP) When curl is told to read cookies from a given file, this option makes it dis‐\ncard all \"session cookies\". This has the same effect as if a new session is started.\nTypical browsers discard session cookies when they are closed down.\n\nProviding -j, --junk-session-cookies multiple times has no extra effect. Disable it\nagain with --no-junk-session-cookies.\n\nExample:\ncurl --junk-session-cookies -b cookies.txt https://example.com\n\nSee also -b, --cookie and -c, --cookie-jar.\n", "flag": "-j", "long": "--junk-session-cookies" }, { "name": "--keepalive-time ", "content": "This option sets the time a connection needs to remain idle before sending keepalive\nprobes and the time between individual keepalive probes. It is currently effective on\noperating systems offering the TCPKEEPIDLE and TCPKEEPINTVL socket options (meaning\nLinux, recent AIX, HP-UX and more). Keepalives are used by the TCP stack to detect\nbroken networks on idle connections. The number of missed keepalive probes before de‐\nclaring the connection down is OS dependent and is commonly 9 or 10. This option has\nno effect if --no-keepalive is used.\n\nIf unspecified, the option defaults to 60 seconds.\n\nIf --keepalive-time is provided several times, the last set value is used.\n\nExample:\ncurl --keepalive-time 20 https://example.com\n\nSee also --no-keepalive and -m, --max-time.\n", "long": "--keepalive-time", "arg": "" }, { "name": "--key-type ", "content": "(TLS) Private key file type. Specify which type your --key provided private key is.\nDER, PEM, and ENG are supported. If not specified, PEM is assumed.\n\nIf --key-type is provided several times, the last set value is used.\n\nExample:\ncurl --key-type DER --key here https://example.com\n\nSee also --key.\n", "long": "--key-type", "arg": "" }, { "name": "--key ", "content": "(TLS SSH) Private key file name. Allows you to provide your private key in this sepa‐\nrate file. For SSH, if not specified, curl tries the following candidates in order:\n'~/.ssh/idrsa', '~/.ssh/iddsa', './idrsa', './iddsa'.\n\nIf curl is built against OpenSSL library, and the engine pkcs11 is available, then a\nPKCS#11 URI (RFC 7512) can be used to specify a private key located in a PKCS#11 de‐\nvice. A string beginning with \"pkcs11:\" is interpreted as a PKCS#11 URI. If a PKCS#11\nURI is provided, then the --engine option is set as \"pkcs11\" if none was provided and\nthe --key-type option is set as \"ENG\" if none was provided.\n\nIf curl is built against Secure Transport or Schannel then this option is ignored for\nTLS protocols (HTTPS, etc). Those backends expect the private key to be already\npresent in the keychain or PKCS#12 file containing the certificate.\n\nIf --key is provided several times, the last set value is used.\n\nExample:\ncurl --cert certificate --key here https://example.com\n\nSee also --key-type and -E, --cert.\n", "long": "--key", "arg": "" }, { "name": "--krb ", "content": "(FTP) Enable Kerberos authentication and use. The level must be entered and should be\none of 'clear', 'safe', 'confidential', or 'private'. Should you use a level that is\nnot one of these, 'private' is used.\n\nIf --krb is provided several times, the last set value is used.\n\nExample:\ncurl --krb clear ftp://example.com/\n\nSee also --delegation and --ssl. --krb requires that the underlying libcurl was built\nto support Kerberos.\n", "long": "--krb", "arg": "" }, { "name": "--libcurl ", "content": "Append this option to any ordinary curl command line, and you get libcurl-using C\nsource code written to the file that does the equivalent of what your command-line op‐\neration does!\n\nThis option is global and does not need to be specified for each use of --next.\n\nIf --libcurl is provided several times, the last set value is used.\n\nExample:\ncurl --libcurl client.c https://example.com\n\nSee also -v, --verbose.\n", "long": "--libcurl", "arg": "" }, { "name": "--limit-rate ", "content": "Specify the maximum transfer rate you want curl to use - for both downloads and up‐\nloads. This feature is useful if you have a limited pipe and you would like your\ntransfer not to use your entire bandwidth. To make it slower than it otherwise would\nbe.\n\nThe given speed is measured in bytes/second, unless a suffix is appended. Appending\n'k' or 'K' counts the number as kilobytes, 'm' or 'M' makes it megabytes, while 'g' or\n'G' makes it gigabytes. The suffixes (k, M, G, T, P) are 1024 based. For example 1k is\n1024. Examples: 200K, 3m and 1G.\n\nThe rate limiting logic works on averaging the transfer speed to no more than the set\nthreshold over a period of multiple seconds.\n\nIf you also use the -Y, --speed-limit option, that option takes precedence and might\ncripple the rate-limiting slightly, to help keeping the speed-limit logic working.\n\nIf --limit-rate is provided several times, the last set value is used.\n\nExamples:\ncurl --limit-rate 100K https://example.com\ncurl --limit-rate 1000 https://example.com\ncurl --limit-rate 10M https://example.com\n\nSee also --rate, -Y, --speed-limit and -y, --speed-time.\n", "long": "--limit-rate", "arg": "" }, { "name": "-l, --list-only", "content": "(FTP POP3 SFTP) (FTP) When listing an FTP directory, this switch forces a name-only\nview. This is especially useful if the user wants to machine-parse the contents of an\nFTP directory since the normal directory view does not use a standard look or format.\nWhen used like this, the option causes an NLST command to be sent to the server in‐\nstead of LIST.\n\nNote: Some FTP servers list only files in their response to NLST; they do not include\nsub-directories and symbolic links.\n\n(SFTP) When listing an SFTP directory, this switch forces a name-only view, one per\nline. This is especially useful if the user wants to machine-parse the contents of an\nSFTP directory since the normal directory view provides more information than just\nfile names.\n\n(POP3) When retrieving a specific email from POP3, this switch forces a LIST command\nto be performed instead of RETR. This is particularly useful if the user wants to see\nif a specific message-id exists on the server and what size it is.\n\nNote: When combined with -X, --request, this option can be used to send a UIDL command\ninstead, so the user may use the email's unique identifier rather than its message-id\nto make the request.\n\nProviding -l, --list-only multiple times has no extra effect. Disable it again with\n--no-list-only.\n\nExample:\ncurl --list-only ftp://example.com/dir/\n\nSee also -Q, --quote and -X, --request.\n", "flag": "-l", "long": "--list-only" }, { "name": "--local-port ", "content": "Set a preferred single number or range (FROM-TO) of local port numbers to use for the\nconnection(s). Note that port numbers by nature are a scarce resource so setting this\nrange to something too narrow might cause unnecessary connection setup failures.\n\nIf --local-port is provided several times, the last set value is used.\n\nExample:\ncurl --local-port 1000-3000 https://example.com\n\nSee also -g, --globoff.\n", "long": "--local-port", "arg": "" }, { "name": "--location-trusted", "content": "(HTTP) Like -L, --location, but allows sending the name + password to all hosts that\nthe site may redirect to. This may or may not introduce a security breach if the site\nredirects you to a site to which you send your authentication info (which is plaintext\nin the case of HTTP Basic authentication).\n\nProviding --location-trusted multiple times has no extra effect. Disable it again\nwith --no-location-trusted.\n\nExample:\ncurl --location-trusted -u user:password https://example.com\n\nSee also -u, --user.\n", "long": "--location-trusted" }, { "name": "-L, --location", "content": "(HTTP) If the server reports that the requested page has moved to a different location\n(indicated with a Location: header and a 3XX response code), this option makes curl\nredo the request on the new place. If used together with -i, --include or -I, --head,\nheaders from all requested pages are shown.\n\nWhen authentication is used, curl only sends its credentials to the initial host. If a\nredirect takes curl to a different host, it does not get the user+password pass on.\nSee also --location-trusted on how to change this.\n\nLimit the amount of redirects to follow by using the --max-redirs option.\n\nWhen curl follows a redirect and if the request is a POST, it sends the following re‐\nquest with a GET if the HTTP response was 301, 302, or 303. If the response code was\nany other 3xx code, curl resends the following request using the same unmodified\nmethod.\n\nYou can tell curl to not change POST requests to GET after a 30x response by using the\ndedicated options for that: --post301, --post302 and --post303.\n\nThe method set with -X, --request overrides the method curl would otherwise select to\nuse.\n\nProviding -L, --location multiple times has no extra effect. Disable it again with\n--no-location.\n\nExample:\ncurl -L https://example.com\n\nSee also --resolve and --alt-svc.\n", "flag": "-L", "long": "--location" }, { "name": "--login-options ", "content": "(IMAP LDAP POP3 SMTP) Specify the login options to use during server authentication.\n\nYou can use login options to specify protocol specific options that may be used during\nauthentication. At present only IMAP, POP3 and SMTP support login options. For more\ninformation about login options please see RFC 2384, RFC 5092 and the IETF draft\nhttps://datatracker.ietf.org/doc/html/draft-earhart-url-smtp-00.\n\nSince 8.2.0, IMAP supports the login option \"AUTH=+LOGIN\". With this option, curl uses\nthe plain (not SASL) LOGIN IMAP command even if the server advertises SASL authentica‐\ntion. Care should be taken in using this option, as it sends your password over the\nnetwork in plain text. This does not work if the IMAP server disables the plain LOGIN\n(e.g. to prevent password snooping).\n\nIf --login-options is provided several times, the last set value is used.\n\nExample:\ncurl --login-options 'AUTH=*' imap://example.com\n\nSee also -u, --user.\n", "long": "--login-options", "arg": "" }, { "name": "--mail-auth
", "content": "(SMTP) Specify a single address. This is used to specify the authentication address\n(identity) of a submitted message that is being relayed to another server.\n\nIf --mail-auth is provided several times, the last set value is used.\n\nExample:\ncurl --mail-auth user@example.come -T mail smtp://example.com/\n\nSee also --mail-rcpt and --mail-from.\n", "long": "--mail-auth", "arg": "
" }, { "name": "--mail-from
", "content": "(SMTP) Specify a single address that the given mail should get sent from.\n\nIf --mail-from is provided several times, the last set value is used.\n\nExample:\ncurl --mail-from user@example.com -T mail smtp://example.com/\n\nSee also --mail-rcpt and --mail-auth.\n", "long": "--mail-from", "arg": "
" }, { "name": "--mail-rcpt-allowfails", "content": "(SMTP) When sending data to multiple recipients, by default curl aborts SMTP conversa‐\ntion if at least one of the recipients causes RCPT TO command to return an error.\n\nThe default behavior can be changed by passing --mail-rcpt-allowfails command-line op‐\ntion which makes curl ignore errors and proceed with the remaining valid recipients.\n\nIf all recipients trigger RCPT TO failures and this flag is specified, curl still\naborts the SMTP conversation and returns the error received from to the last RCPT TO\ncommand.\n\nProviding --mail-rcpt-allowfails multiple times has no extra effect. Disable it again\nwith --no-mail-rcpt-allowfails.\n\nExample:\ncurl --mail-rcpt-allowfails --mail-rcpt dest@example.com smtp://example.com\n\nSee also --mail-rcpt. Added in 7.69.0.\n", "long": "--mail-rcpt-allowfails" }, { "name": "--mail-rcpt
", "content": "(SMTP) Specify a single email address, user name or mailing list name. Repeat this op‐\ntion several times to send to multiple recipients.\n\nWhen performing an address verification (VRFY command), the recipient should be speci‐\nfied as the user name or user name and domain (as per Section 3.5 of RFC 5321).\n\nWhen performing a mailing list expand (EXPN command), the recipient should be speci‐\nfied using the mailing list name, such as \"Friends\" or \"London-Office\".\n\n\n--mail-rcpt can be used several times in a command line\n\nExample:\ncurl --mail-rcpt user@example.net smtp://example.com\n\nSee also --mail-rcpt-allowfails.\n", "long": "--mail-rcpt", "arg": "
" }, { "name": "-M, --manual", "content": "Manual. Display the huge help text.\n\nExample:\ncurl --manual\n\nSee also -v, --verbose, --libcurl and --trace.\n", "flag": "-M", "long": "--manual" }, { "name": "--max-filesize ", "content": "(FTP HTTP MQTT) Specify the maximum size (in bytes) of a file to download. If the file\nrequested is larger than this value, the transfer does not start and curl returns with\nexit code 63.\n\nA size modifier may be used. For example, Appending 'k' or 'K' counts the number as\nkilobytes, 'm' or 'M' makes it megabytes, while 'g' or 'G' makes it gigabytes. Exam‐\nples: 200K, 3m and 1G. (Added in 7.58.0)\n\nNOTE: before curl 8.4.0, when the file size is not known prior to download, for such\nfiles this option has no effect even if the file transfer ends up being larger than\nthis given limit.\n\nStarting with curl 8.4.0, this option aborts the transfer if it reaches the threshold\nduring transfer.\n\nIf --max-filesize is provided several times, the last set value is used.\n\nExample:\ncurl --max-filesize 100K https://example.com\n\nSee also --limit-rate.\n", "long": "--max-filesize", "arg": "" }, { "name": "--max-redirs ", "content": "(HTTP) Set maximum number of redirections to follow. When -L, --location is used, to\nprevent curl from following too many redirects, by default, the limit is set to 50\nredirects. Set this option to -1 to make it unlimited.\n\nIf --max-redirs is provided several times, the last set value is used.\n\nExample:\ncurl --max-redirs 3 --location https://example.com\n\nSee also -L, --location.\n", "long": "--max-redirs", "arg": "" }, { "name": "-m, --max-time ", "content": "Maximum time in seconds that you allow each transfer to take. This is useful for pre‐\nventing your batch jobs from hanging for hours due to slow networks or links going\ndown. This option accepts decimal values.\n\nIf you enable retrying the transfer (--retry) then the maximum time counter is reset\neach time the transfer is retried. You can use --retry-max-time to limit the retry\ntime.\n\nThe decimal value needs to provided using a dot (.) as decimal separator - not the lo‐\ncal version even if it might be using another separator.\n\nIf -m, --max-time is provided several times, the last set value is used.\n\nExamples:\ncurl --max-time 10 https://example.com\ncurl --max-time 2.92 https://example.com\n\nSee also --connect-timeout and --retry-max-time.\n", "flag": "-m", "long": "--max-time" }, { "name": "--metalink", "content": "This option was previously used to specify a Metalink resource. Metalink support is\ndisabled in curl for security reasons (added in 7.78.0).\n\nIf --metalink is provided several times, the last set value is used.\n\nExample:\ncurl --metalink file https://example.com\n\nSee also -Z, --parallel.\n", "long": "--metalink" }, { "name": "--negotiate", "content": "(HTTP) Enables Negotiate (SPNEGO) authentication.\n\nThis option requires a library built with GSS-API or SSPI support. Use -V, --version\nto see if your curl supports GSS-API/SSPI or SPNEGO.\n\nWhen using this option, you must also provide a fake -u, --user option to activate the\nauthentication code properly. Sending a '-u :' is enough as the user name and password\nfrom the -u, --user option are not actually used.\n\nProviding --negotiate multiple times has no extra effect.\n\nExample:\ncurl --negotiate -u : https://example.com\n\nSee also --basic, --ntlm, --anyauth and --proxy-negotiate.\n", "long": "--negotiate" }, { "name": "--netrc-file ", "content": "This option is similar to -n, --netrc, except that you provide the path (absolute or\nrelative) to the netrc file that curl should use. You can only specify one netrc file\nper invocation.\n\nIt abides by --netrc-optional if specified.\n\nIf --netrc-file is provided several times, the last set value is used.\n\nExample:\ncurl --netrc-file netrc https://example.com\n\nSee also -n, --netrc, -u, --user and -K, --config. This option is mutually exclusive\nto -n, --netrc.\n", "long": "--netrc-file", "arg": "" }, { "name": "--netrc-optional", "content": "Similar to -n, --netrc, but this option makes the .netrc usage optional and not manda‐\ntory as the -n, --netrc option does.\n\nProviding --netrc-optional multiple times has no extra effect. Disable it again with\n--no-netrc-optional.\n\nExample:\ncurl --netrc-optional https://example.com\n\nSee also --netrc-file. This option is mutually exclusive to -n, --netrc.\n", "long": "--netrc-optional" }, { "name": "-n, --netrc", "content": "Makes curl scan the .netrc file in the user's home directory for login name and pass‐\nword. This is typically used for FTP on Unix. If used with HTTP, curl enables user au‐\nthentication. See netrc(5) and ftp(1) for details on the file format. Curl does not\ncomplain if that file does not have the right permissions (it should be neither world-\nnor group-readable). The environment variable \"HOME\" is used to find the home direc‐\ntory.\n\nOn Windows two filenames in the home directory are checked: .netrc and netrc, prefer‐\nring the former. Older versions on Windows checked for netrc only.\n\nA quick and simple example of how to setup a .netrc to allow curl to FTP to the ma‐\nchine host.domain.com with user name 'myself' and password 'secret' could look similar\nto:\n\nmachine host.domain.com\nlogin myself\npassword secret\n\nProviding -n, --netrc multiple times has no extra effect. Disable it again with\n--no-netrc.\n\nExample:\ncurl --netrc https://example.com\n\nSee also --netrc-file, -K, --config and -u, --user. This option is mutually exclusive\nto --netrc-file and --netrc-optional.\n\n-:, --next\nTells curl to use a separate operation for the following URL and associated options.\nThis allows you to send several URL requests, each with their own specific options,\nfor example, such as different user names or custom requests for each.\n\n-:, --next resets all local options and only global ones have their values survive\nover to the operation following the -:, --next instruction. Global options include -v,\n--verbose, --trace, --trace-ascii and --fail-early.\n\nFor example, you can do both a GET and a POST in a single command line:\n\ncurl www1.example.com --next -d postthis www2.example.com\n\n-:, --next can be used several times in a command line\n\nExamples:\ncurl https://example.com --next -d postthis www2.example.com\ncurl -I https://example.com --next https://example.net/\n\nSee also -Z, --parallel and -K, --config.\n", "flag": "-n", "long": "--netrc" }, { "name": "--no-alpn", "content": "(HTTPS) Disable the ALPN TLS extension. ALPN is enabled by default if libcurl was\nbuilt with an SSL library that supports ALPN. ALPN is used by a libcurl that supports\nHTTP/2 to negotiate HTTP/2 support with the server during https sessions.\n\nNote that this is the negated option name documented. You can use --alpn to enable\nALPN.\n\nProviding --no-alpn multiple times has no extra effect. Disable it again with --alpn.\n\nExample:\ncurl --no-alpn https://example.com\n\nSee also --no-npn and --http2. --no-alpn requires that the underlying libcurl was\nbuilt to support TLS.\n", "long": "--no-alpn" }, { "name": "-N, --no-buffer", "content": "Disables the buffering of the output stream. In normal work situations, curl uses a\nstandard buffered output stream that has the effect that it outputs the data in\nchunks, not necessarily exactly when the data arrives. Using this option disables that\nbuffering.\n\nNote that this is the negated option name documented. You can use --buffer to enable\nbuffering again.\n\nProviding -N, --no-buffer multiple times has no extra effect. Disable it again with\n--buffer.\n\nExample:\ncurl --no-buffer https://example.com\n\nSee also -#, --progress-bar.\n", "flag": "-N", "long": "--no-buffer" }, { "name": "--no-clobber", "content": "When used in conjunction with the -o, --output, -J, --remote-header-name, -O, --re‐\nmote-name, or --remote-name-all options, curl avoids overwriting files that already\nexist. Instead, a dot and a number gets appended to the name of the file that would be\ncreated, up to filename.100 after which it does not create any file.\n\nNote that this is the negated option name documented. You can thus use --clobber to\nenforce the clobbering, even if -J, --remote-header-name is specified.\n\nProviding --no-clobber multiple times has no extra effect. Disable it again with\n--clobber.\n\nExample:\ncurl --no-clobber --output local/dir/file https://example.com\n\nSee also -o, --output and -O, --remote-name. Added in 7.83.0.\n", "long": "--no-clobber" }, { "name": "--no-keepalive", "content": "Disables the use of keepalive messages on the TCP connection. curl otherwise enables\nthem by default.\n\nNote that this is the negated option name documented. You can thus use --keepalive to\nenforce keepalive.\n\nProviding --no-keepalive multiple times has no extra effect. Disable it again with\n--keepalive.\n\nExample:\ncurl --no-keepalive https://example.com\n\nSee also --keepalive-time.\n", "long": "--no-keepalive" }, { "name": "--no-npn", "content": "(HTTPS) curl never uses NPN, this option has no effect (added in 7.86.0).\n\nDisable the NPN TLS extension. NPN is enabled by default if libcurl was built with an\nSSL library that supports NPN. NPN is used by a libcurl that supports HTTP/2 to nego‐\ntiate HTTP/2 support with the server during https sessions.\n\nProviding --no-npn multiple times has no extra effect. Disable it again with --npn.\n\nExample:\ncurl --no-npn https://example.com\n\nSee also --no-alpn and --http2. --no-npn requires that the underlying libcurl was\nbuilt to support TLS.\n", "long": "--no-npn" }, { "name": "--no-progress-meter", "content": "Option to switch off the progress meter output without muting or otherwise affecting\nwarning and informational messages like -s, --silent does.\n\nNote that this is the negated option name documented. You can thus use --progress-me‐\nter to enable the progress meter again.\n\nProviding --no-progress-meter multiple times has no extra effect. Disable it again\nwith --progress-meter.\n\nExample:\ncurl --no-progress-meter -o store https://example.com\n\nSee also -v, --verbose and -s, --silent. Added in 7.67.0.\n", "long": "--no-progress-meter" }, { "name": "--no-sessionid", "content": "(TLS) Disable curl's use of SSL session-ID caching. By default all transfers are done\nusing the cache. Note that while nothing should ever get hurt by attempting to reuse\nSSL session-IDs, there seem to be broken SSL implementations in the wild that may re‐\nquire you to disable this in order for you to succeed.\n\nNote that this is the negated option name documented. You can thus use --sessionid to\nenforce session-ID caching.\n\nProviding --no-sessionid multiple times has no extra effect. Disable it again with\n--sessionid.\n\nExample:\ncurl --no-sessionid https://example.com\n\nSee also -k, --insecure.\n", "long": "--no-sessionid" }, { "name": "--noproxy ", "content": "Comma-separated list of hosts for which not to use a proxy, if one is specified. The\nonly wildcard is a single * character, which matches all hosts, and effectively dis‐\nables the proxy. Each name in this list is matched as either a domain which contains\nthe hostname, or the hostname itself. For example, local.com would match local.com,\nlocal.com:80, and www.local.com, but not www.notlocal.com.\n\nThis option overrides the environment variables that disable the proxy ('noproxy' and\n'NOPROXY') (added in 7.53.0). If there is an environment variable disabling a proxy,\nyou can set the no proxy list to \"\" to override it.\n\nIP addresses specified to this option can be provided using CIDR notation (added in\n7.86.0): an appended slash and number specifies the number of \"network bits\" out of\nthe address to use in the comparison. For example \"192.168.0.0/16\" would match all ad‐\ndresses starting with \"192.168\".\n\nIf --noproxy is provided several times, the last set value is used.\n\nExample:\ncurl --noproxy \"www.example\" https://example.com\n\nSee also -x, --proxy.\n", "long": "--noproxy", "arg": "" }, { "name": "--ntlm-wb", "content": "(HTTP) Enables NTLM much in the style --ntlm does, but hand over the authentication to\nthe separate binary ntlmauth application that is executed when needed.\n\nProviding --ntlm-wb multiple times has no extra effect.\n\nExample:\ncurl --ntlm-wb -u user:password https://example.com\n\nSee also --ntlm and --proxy-ntlm.\n\n--ntlm (HTTP) Enables NTLM authentication. The NTLM authentication method was designed by Mi‐\ncrosoft and is used by IIS web servers. It is a proprietary protocol, reverse-engi‐\nneered by clever people and implemented in curl based on their efforts. This kind of\nbehavior should not be endorsed, you should encourage everyone who uses NTLM to switch\nto a public and documented authentication method instead, such as Digest.\n\nIf you want to enable NTLM for your proxy authentication, then use --proxy-ntlm.\n\nProviding --ntlm multiple times has no extra effect.\n\nExample:\ncurl --ntlm -u user:password https://example.com\n\nSee also --proxy-ntlm. --ntlm requires that the underlying libcurl was built to sup‐\nport TLS. This option is mutually exclusive to --basic and --negotiate and --digest\nand --anyauth.\n", "long": "--ntlm-wb" }, { "name": "--oauth2-bearer ", "content": "(IMAP LDAP POP3 SMTP HTTP) Specify the Bearer Token for OAUTH 2.0 server authentica‐\ntion. The Bearer Token is used in conjunction with the user name which can be speci‐\nfied as part of the --url or -u, --user options.\n\nThe Bearer Token and user name are formatted according to RFC 6750.\n\nIf --oauth2-bearer is provided several times, the last set value is used.\n\nExample:\ncurl --oauth2-bearer \"mF9.B5f-4.1JqM\" https://example.com\n\nSee also --basic, --ntlm and --digest.\n", "long": "--oauth2-bearer", "arg": "" }, { "name": "--output-dir ", "content": "This option specifies the directory in which files should be stored, when -O, --re‐\nmote-name or -o, --output are used.\n\nThe given output directory is used for all URLs and output options on the command\nline, up until the first -:, --next.\n\nIf the specified target directory does not exist, the operation fails unless --cre‐\nate-dirs is also used.\n\nIf --output-dir is provided several times, the last set value is used.\n\nExample:\ncurl --output-dir \"tmp\" -O https://example.com\n\nSee also -O, --remote-name and -J, --remote-header-name. Added in 7.73.0.\n", "long": "--output-dir", "arg": "" }, { "name": "-o, --output ", "content": "Write output to instead of stdout. If you are using {} or [] to fetch multiple\ndocuments, you should quote the URL and you can use '#' followed by a number in the\n specifier. That variable is replaced with the current string for the URL being\nfetched. Like in:\n\ncurl \"http://{one,two}.example.com\" -o \"file#1.txt\"\n\nor use several variables like:\n\ncurl \"http://{site,host}.host[1-5].example\" -o \"#1#2\"\n\nYou may use this option as many times as the number of URLs you have. For example, if\nyou specify two URLs on the same command line, you can use it like this:\n\ncurl -o aa example.com -o bb example.net\n\nand the order of the -o options and the URLs does not matter, just that the first -o\nis for the first URL and so on, so the above command line can also be written as\n\ncurl example.com example.net -o aa -o bb\n\nSee also the --create-dirs option to create the local directories dynamically. Speci‐\nfying the output as '-' (a single dash) passes the output to stdout.\n\nTo suppress response bodies, you can redirect output to /dev/null:\n\ncurl example.com -o /dev/null\n\nOr for Windows:\n\ncurl example.com -o nul\n\n-o, --output can be used several times in a command line\n\nExamples:\ncurl -o file https://example.com\ncurl \"http://{one,two}.example.com\" -o \"file#1.txt\"\ncurl \"http://{site,host}.host[1-5].example\" -o \"#1#2\"\ncurl -o file https://example.com -o file2 https://example.net\n\nSee also -O, --remote-name, --remote-name-all and -J, --remote-header-name.\n", "flag": "-o", "long": "--output", "arg": "" }, { "name": "--parallel-immediate", "content": "When doing parallel transfers, this option instructs curl that it should rather prefer\nopening up more connections in parallel at once rather than waiting to see if new\ntransfers can be added as multiplexed streams on another connection.\n\nThis option is global and does not need to be specified for each use of --next.\n\nProviding --parallel-immediate multiple times has no extra effect. Disable it again\nwith --no-parallel-immediate.\n\nExample:\ncurl --parallel-immediate -Z https://example.com -o file1 https://example.com -o file2\n\nSee also -Z, --parallel and --parallel-max. Added in 7.68.0.\n", "long": "--parallel-immediate" }, { "name": "--parallel-max ", "content": "When asked to do parallel transfers, using -Z, --parallel, this option controls the\nmaximum amount of transfers to do simultaneously.\n\nThis option is global and does not need to be specified for each use of -:, --next.\n\nThe default is 50.\n\nIf --parallel-max is provided several times, the last set value is used.\n\nExample:\ncurl --parallel-max 100 -Z https://example.com ftp://example.com/\n\nSee also -Z, --parallel. Added in 7.66.0.\n", "long": "--parallel-max", "arg": "" }, { "name": "-Z, --parallel", "content": "Makes curl perform its transfers in parallel as compared to the regular serial manner.\n\nThis option is global and does not need to be specified for each use of --next.\n\nProviding -Z, --parallel multiple times has no extra effect. Disable it again with\n--no-parallel.\n\nExample:\ncurl --parallel https://example.com -o file1 https://example.com -o file2\n\nSee also -:, --next and -v, --verbose. Added in 7.66.0.\n", "flag": "-Z", "long": "--parallel" }, { "name": "--pass ", "content": "(SSH TLS) Passphrase for the private key.\n\nIf --pass is provided several times, the last set value is used.\n\nExample:\ncurl --pass secret --key file https://example.com\n\nSee also --key and -u, --user.\n", "long": "--pass", "arg": "" }, { "name": "--path-as-is", "content": "Tell curl to not handle sequences of /../ or /./ in the given URL path. Normally curl\nsquashes or merges them according to standards but with this option set you tell it\nnot to do that.\n\nProviding --path-as-is multiple times has no extra effect. Disable it again with\n--no-path-as-is.\n\nExample:\ncurl --path-as-is https://example.com/../../etc/passwd\n\nSee also --request-target.\n", "long": "--path-as-is" }, { "name": "--pinnedpubkey ", "content": "(TLS) Tells curl to use the specified public key file (or hashes) to verify the peer.\nThis can be a path to a file which contains a single public key in PEM or DER format,\nor any number of base64 encoded sha256 hashes preceded by 'sha256//' and separated by\n';'.\n\nWhen negotiating a TLS or SSL connection, the server sends a certificate indicating\nits identity. A public key is extracted from this certificate and if it does not ex‐\nactly match the public key provided to this option, curl aborts the connection before\nsending or receiving any data.\n\nThis option is independent of option -k, --insecure. If you use both options together\nthen the peer is still verified by public key.\n\nPEM/DER support:\n\nOpenSSL and GnuTLS, wolfSSL (added in 7.43.0), mbedTLS , Secure Transport macOS\n10.7+/iOS 10+ (7.54.1), Schannel (7.58.1)\n\nsha256 support:\n\nOpenSSL, GnuTLS and wolfSSL, mbedTLS (added in 7.47.0), Secure Transport macOS\n10.7+/iOS 10+ (7.54.1), Schannel (7.58.1)\n\nOther SSL backends not supported.\n\nIf --pinnedpubkey is provided several times, the last set value is used.\n\nExamples:\ncurl --pinnedpubkey keyfile https://example.com\ncurl --pinnedpubkey 'sha256//ce118b51897f4452dc' https://example.com\n\nSee also --hostpubsha256.\n", "long": "--pinnedpubkey", "arg": "" }, { "name": "--post301", "content": "(HTTP) Tells curl to respect RFC 7231/6.4.2 and not convert POST requests into GET re‐\nquests when following a 301 redirection. The non-RFC behavior is ubiquitous in web\nbrowsers, so curl does the conversion by default to maintain consistency. However, a\nserver may require a POST to remain a POST after such a redirection. This option is\nmeaningful only when using -L, --location.\n\nProviding --post301 multiple times has no extra effect. Disable it again with\n--no-post301.\n\nExample:\ncurl --post301 --location -d \"data\" https://example.com\n\nSee also --post302, --post303 and -L, --location.\n", "long": "--post301" }, { "name": "--post302", "content": "(HTTP) Tells curl to respect RFC 7231/6.4.3 and not convert POST requests into GET re‐\nquests when following a 302 redirection. The non-RFC behavior is ubiquitous in web\nbrowsers, so curl does the conversion by default to maintain consistency. However, a\nserver may require a POST to remain a POST after such a redirection. This option is\nmeaningful only when using -L, --location.\n\nProviding --post302 multiple times has no extra effect. Disable it again with\n--no-post302.\n\nExample:\ncurl --post302 --location -d \"data\" https://example.com\n\nSee also --post301, --post303 and -L, --location.\n", "long": "--post302" }, { "name": "--post303", "content": "(HTTP) Tells curl to violate RFC 7231/6.4.4 and not convert POST requests into GET re‐\nquests when following 303 redirections. A server may require a POST to remain a POST\nafter a 303 redirection. This option is meaningful only when using -L, --location.\n\nProviding --post303 multiple times has no extra effect. Disable it again with\n--no-post303.\n\nExample:\ncurl --post303 --location -d \"data\" https://example.com\n\nSee also --post302, --post301 and -L, --location.\n\n--preproxy [protocol://]host[:port]\nUse the specified SOCKS proxy before connecting to an HTTP or HTTPS -x, --proxy. In\nsuch a case curl first connects to the SOCKS proxy and then connects (through SOCKS)\nto the HTTP or HTTPS proxy. Hence pre proxy.\n\nThe pre proxy string should be specified with a protocol:// prefix to specify alterna‐\ntive proxy protocols. Use socks4://, socks4a://, socks5:// or socks5h:// to request\nthe specific SOCKS version to be used. No protocol specified makes curl default to\nSOCKS4.\n\nIf the port number is not specified in the proxy string, it is assumed to be 1080.\n\nUser and password that might be provided in the proxy string are URL decoded by curl.\nThis allows you to pass in special characters such as @ by using %40 or pass in a\ncolon with %3a.\n\nIf --preproxy is provided several times, the last set value is used.\n\nExample:\ncurl --preproxy socks5://proxy.example -x http://http.example https://example.com\n\nSee also -x, --proxy and --socks5. Added in 7.52.0.\n\n-#, --progress-bar\nMake curl display transfer progress as a simple progress bar instead of the standard,\nmore informational, meter.\n\nThis progress bar draws a single line of '#' characters across the screen and shows a\npercentage if the transfer size is known. For transfers without a known size, there is\na space ship (-=o=-) that moves back and forth but only while data is being trans‐\nferred, with a set of flying hash sign symbols on top.\n\nThis option is global and does not need to be specified for each use of --next.\n\nProviding -#, --progress-bar multiple times has no extra effect. Disable it again\nwith --no-progress-bar.\n\nExample:\ncurl -# -O https://example.com\n\nSee also --styled-output.\n", "long": "--post303" }, { "name": "--proto-default ", "content": "Tells curl to use protocol for any URL missing a scheme name.\n\nAn unknown or unsupported protocol causes error CURLEUNSUPPORTEDPROTOCOL (1).\n\nThis option does not change the default proxy protocol (http).\n\nWithout this option set, curl guesses protocol based on the host name, see --url for\ndetails.\n\nIf --proto-default is provided several times, the last set value is used.\n\nExample:\ncurl --proto-default https ftp.example.com\n\nSee also --proto and --proto-redir.\n", "long": "--proto-default", "arg": "" }, { "name": "--proto-redir ", "content": "Tells curl to limit what protocols it may use on redirect. Protocols denied by --proto\nare not overridden by this option. See --proto for how protocols are represented.\n\nExample, allow only HTTP and HTTPS on redirect:\n\ncurl --proto-redir -all,http,https http://example.com\n\nBy default curl only allows HTTP, HTTPS, FTP and FTPS on redirects (added in 7.65.2).\nSpecifying all or +all enables all protocols on redirects, which is not good for secu‐\nrity.\n\nIf --proto-redir is provided several times, the last set value is used.\n\nExample:\ncurl --proto-redir =http,https https://example.com\n\nSee also --proto.\n", "long": "--proto-redir", "arg": "" }, { "name": "--proto ", "content": "Tells curl to limit what protocols it may use for transfers. Protocols are evaluated\nleft to right, are comma separated, and are each a protocol name or 'all', optionally\nprefixed by zero or more modifiers. Available modifiers are:\n\n+ Permit this protocol in addition to protocols already permitted (this is the de‐\nfault if no modifier is used).\n\n- Deny this protocol, removing it from the list of protocols already permitted.\n\n= Permit only this protocol (ignoring the list already permitted), though subject to\nlater modification by subsequent entries in the comma separated list.\n\nFor example:\n\n--proto -ftps uses the default protocols, but disables ftps\n\n--proto -all,https,+http\nonly enables http and https\n\n--proto =http,https\nalso only enables http and https\n\nUnknown and disabled protocols produce a warning. This allows scripts to safely rely\non being able to disable potentially dangerous protocols, without relying upon support\nfor that protocol being built into curl to avoid an error.\n\nThis option can be used multiple times, in which case the effect is the same as con‐\ncatenating the protocols into one instance of the option.\n\nIf --proto is provided several times, the last set value is used.\n\nExample:\ncurl --proto =http,https,sftp https://example.com\n\nSee also --proto-redir and --proto-default.\n", "long": "--proto", "arg": "" }, { "name": "--proxy-anyauth", "content": "Tells curl to pick a suitable authentication method when communicating with the given\nHTTP proxy. This might cause an extra request/response round-trip.\n\nProviding --proxy-anyauth multiple times has no extra effect.\n\nExample:\ncurl --proxy-anyauth --proxy-user user:passwd -x proxy https://example.com\n\nSee also -x, --proxy, --proxy-basic and --proxy-digest.\n", "long": "--proxy-anyauth" }, { "name": "--proxy-basic", "content": "Tells curl to use HTTP Basic authentication when communicating with the given proxy.\nUse --basic for enabling HTTP Basic with a remote host. Basic is the default authenti‐\ncation method curl uses with proxies.\n\nProviding --proxy-basic multiple times has no extra effect.\n\nExample:\ncurl --proxy-basic --proxy-user user:passwd -x proxy https://example.com\n\nSee also -x, --proxy, --proxy-anyauth and --proxy-digest.\n", "long": "--proxy-basic" }, { "name": "--proxy-ca-native", "content": "(TLS) Tells curl to use the CA store from the native operating system to verify the\nHTTPS proxy. By default, curl uses a CA store provided in a single file or directory,\nbut when using this option it interfaces the operating system's own vault.\n\nThis option only works for curl on Windows when built to use OpenSSL. When curl on\nWindows is built to use Schannel, this feature is implied and curl then only uses the\nnative CA store.\n\ncurl built with wolfSSL also supports this option (added in 8.3.0).\n\nProviding --proxy-ca-native multiple times has no extra effect. Disable it again with\n--no-proxy-ca-native.\n\nExample:\ncurl --ca-native https://example.com\n\nSee also --cacert, --capath and -k, --insecure. Added in 8.2.0.\n", "long": "--proxy-ca-native" }, { "name": "--proxy-cacert ", "content": "Same as --cacert but used in HTTPS proxy context.\n\nIf --proxy-cacert is provided several times, the last set value is used.\n\nExample:\ncurl --proxy-cacert CA-file.txt -x https://proxy https://example.com\n\nSee also --proxy-capath, --cacert, --capath and -x, --proxy. Added in 7.52.0.\n", "long": "--proxy-cacert", "arg": "" }, { "name": "--proxy-capath ", "content": "Same as --capath but used in HTTPS proxy context.\n\nIf --proxy-capath is provided several times, the last set value is used.\n\nExample:\ncurl --proxy-capath /local/directory -x https://proxy https://example.com\n\nSee also --proxy-cacert, -x, --proxy and --capath. Added in 7.52.0.\n", "long": "--proxy-capath", "arg": "" }, { "name": "--proxy-cert-type ", "content": "Same as --cert-type but used in HTTPS proxy context.\n\nIf --proxy-cert-type is provided several times, the last set value is used.\n\nExample:\ncurl --proxy-cert-type PEM --proxy-cert file -x https://proxy https://example.com\n\nSee also --proxy-cert. Added in 7.52.0.\n\n--proxy-cert \nSame as -E, --cert but used in HTTPS proxy context.\n\nIf --proxy-cert is provided several times, the last set value is used.\n\nExample:\ncurl --proxy-cert file -x https://proxy https://example.com\n\nSee also --proxy-cert-type. Added in 7.52.0.\n", "long": "--proxy-cert-type", "arg": "" }, { "name": "--proxy-ciphers ", "content": "Same as --ciphers but used in HTTPS proxy context.\n\nSpecifies which ciphers to use in the connection to the HTTPS proxy. The list of ci‐\nphers must specify valid ciphers. Read up on SSL cipher list details on this URL:\n\nhttps://curl.se/docs/ssl-ciphers.html\n\nIf --proxy-ciphers is provided several times, the last set value is used.\n\nExample:\ncurl --proxy-ciphers ECDHE-ECDSA-AES256-CCM8 -x https://proxy https://example.com\n\nSee also --ciphers, --curves and -x, --proxy. Added in 7.52.0.\n", "long": "--proxy-ciphers", "arg": "" }, { "name": "--proxy-crlfile ", "content": "Same as --crlfile but used in HTTPS proxy context.\n\nIf --proxy-crlfile is provided several times, the last set value is used.\n\nExample:\ncurl --proxy-crlfile rejects.txt -x https://proxy https://example.com\n\nSee also --crlfile and -x, --proxy. Added in 7.52.0.\n", "long": "--proxy-crlfile", "arg": "" }, { "name": "--proxy-digest", "content": "Tells curl to use HTTP Digest authentication when communicating with the given proxy.\nUse --digest for enabling HTTP Digest with a remote host.\n\nProviding --proxy-digest multiple times has no extra effect.\n\nExample:\ncurl --proxy-digest --proxy-user user:passwd -x proxy https://example.com\n\nSee also -x, --proxy, --proxy-anyauth and --proxy-basic.\n", "long": "--proxy-digest" }, { "name": "--proxy-header
", "content": "(HTTP) Extra header to include in the request when sending HTTP to a proxy. You may\nspecify any number of extra headers. This is the equivalent option to -H, --header but\nis for proxy communication only like in CONNECT requests when you want a separate\nheader sent to the proxy to what is sent to the actual remote host.\n\ncurl makes sure that each header you add/replace is sent with the proper end-of-line\nmarker, you should thus not add that as a part of the header content: do not add new‐\nlines or carriage returns, they only mess things up for you.\n\nHeaders specified with this option are not included in requests that curl knows are\nnot be sent to a proxy.\n\nThis option can take an argument in @filename style, which then adds a header for each\nline in the input file (added in 7.55.0). Using @- makes curl read the headers from\nstdin.\n\nThis option can be used multiple times to add/replace/remove multiple headers.\n\n--proxy-header can be used several times in a command line\n\nExamples:\ncurl --proxy-header \"X-First-Name: Joe\" -x http://proxy https://example.com\ncurl --proxy-header \"User-Agent: surprise\" -x http://proxy https://example.com\ncurl --proxy-header \"Host:\" -x http://proxy https://example.com\n\nSee also -x, --proxy.\n", "long": "--proxy-header", "arg": "
" }, { "name": "--proxy-http2", "content": "(HTTP) Tells curl to try negotiate HTTP version 2 with an HTTPS proxy. The proxy might\nstill only offer HTTP/1 and then curl sticks to using that version.\n\nThis has no effect for any other kinds of proxies.\n\nProviding --proxy-http2 multiple times has no extra effect. Disable it again with\n--no-proxy-http2.\n\nExample:\ncurl --proxy-http2 -x proxy https://example.com\n\nSee also -x, --proxy. --proxy-http2 requires that the underlying libcurl was built to\nsupport HTTP/2. Added in 8.1.0.\n", "long": "--proxy-http2" }, { "name": "--proxy-insecure", "content": "Same as -k, --insecure but used in HTTPS proxy context.\n\nProviding --proxy-insecure multiple times has no extra effect. Disable it again with\n--no-proxy-insecure.\n\nExample:\ncurl --proxy-insecure -x https://proxy https://example.com\n\nSee also -x, --proxy and -k, --insecure. Added in 7.52.0.\n", "long": "--proxy-insecure" }, { "name": "--proxy-key-type ", "content": "Same as --key-type but used in HTTPS proxy context.\n\nIf --proxy-key-type is provided several times, the last set value is used.\n\nExample:\ncurl --proxy-key-type DER --proxy-key here -x https://proxy https://example.com\n\nSee also --proxy-key and -x, --proxy. Added in 7.52.0.\n", "long": "--proxy-key-type", "arg": "" }, { "name": "--proxy-key ", "content": "Same as --key but used in HTTPS proxy context.\n\nIf --proxy-key is provided several times, the last set value is used.\n\nExample:\ncurl --proxy-key here -x https://proxy https://example.com\n\nSee also --proxy-key-type and -x, --proxy. Added in 7.52.0.\n", "long": "--proxy-key", "arg": "" }, { "name": "--proxy-negotiate", "content": "Tells curl to use HTTP Negotiate (SPNEGO) authentication when communicating with the\ngiven proxy. Use --negotiate for enabling HTTP Negotiate (SPNEGO) with a remote host.\n\nProviding --proxy-negotiate multiple times has no extra effect.\n\nExample:\ncurl --proxy-negotiate --proxy-user user:passwd -x proxy https://example.com\n\nSee also --proxy-anyauth and --proxy-basic.\n", "long": "--proxy-negotiate" }, { "name": "--proxy-ntlm", "content": "Tells curl to use HTTP NTLM authentication when communicating with the given proxy.\nUse --ntlm for enabling NTLM with a remote host.\n\nProviding --proxy-ntlm multiple times has no extra effect.\n\nExample:\ncurl --proxy-ntlm --proxy-user user:passwd -x http://proxy https://example.com\n\nSee also --proxy-negotiate and --proxy-anyauth.\n", "long": "--proxy-ntlm" }, { "name": "--proxy-pass ", "content": "Same as --pass but used in HTTPS proxy context.\n\nIf --proxy-pass is provided several times, the last set value is used.\n\nExample:\ncurl --proxy-pass secret --proxy-key here -x https://proxy https://example.com\n\nSee also -x, --proxy and --proxy-key. Added in 7.52.0.\n", "long": "--proxy-pass", "arg": "" }, { "name": "--proxy-pinnedpubkey ", "content": "(TLS) Tells curl to use the specified public key file (or hashes) to verify the proxy.\nThis can be a path to a file which contains a single public key in PEM or DER format,\nor any number of base64 encoded sha256 hashes preceded by 'sha256//' and separated by\n';'.\n\nWhen negotiating a TLS or SSL connection, the server sends a certificate indicating\nits identity. A public key is extracted from this certificate and if it does not ex‐\nactly match the public key provided to this option, curl aborts the connection before\nsending or receiving any data.\n\nIf --proxy-pinnedpubkey is provided several times, the last set value is used.\n\nExamples:\ncurl --proxy-pinnedpubkey keyfile https://example.com\ncurl --proxy-pinnedpubkey 'sha256//ce118b51897f4452dc' https://example.com\n\nSee also --pinnedpubkey and -x, --proxy. Added in 7.59.0.\n", "long": "--proxy-pinnedpubkey", "arg": "" }, { "name": "--proxy-service-name ", "content": "This option allows you to change the service name for proxy negotiation.\n\nIf --proxy-service-name is provided several times, the last set value is used.\n\nExample:\ncurl --proxy-service-name \"shrubbery\" -x proxy https://example.com\n\nSee also --service-name and -x, --proxy.\n", "long": "--proxy-service-name", "arg": "" }, { "name": "--proxy-ssl-allow-beast", "content": "Same as --ssl-allow-beast but used in HTTPS proxy context.\n\nProviding --proxy-ssl-allow-beast multiple times has no extra effect. Disable it\nagain with --no-proxy-ssl-allow-beast.\n\nExample:\ncurl --proxy-ssl-allow-beast -x https://proxy https://example.com\n\nSee also --ssl-allow-beast and -x, --proxy. Added in 7.52.0.\n", "long": "--proxy-ssl-allow-beast" }, { "name": "--proxy-ssl-auto-client-cert", "content": "Same as --ssl-auto-client-cert but used in HTTPS proxy context.\n\nProviding --proxy-ssl-auto-client-cert multiple times has no extra effect. Disable it\nagain with --no-proxy-ssl-auto-client-cert.\n\nExample:\ncurl --proxy-ssl-auto-client-cert -x https://proxy https://example.com\n\nSee also --ssl-auto-client-cert and -x, --proxy. Added in 7.77.0.\n", "long": "--proxy-ssl-auto-client-cert" }, { "name": "--proxy-tls13-ciphers ", "content": "(TLS) Specifies which cipher suites to use in the connection to your HTTPS proxy when\nit negotiates TLS 1.3. The list of ciphers suites must specify valid ciphers. Read up\non TLS 1.3 cipher suite details on this URL:\n\nhttps://curl.se/docs/ssl-ciphers.html\n\nThis option is currently used only when curl is built to use OpenSSL 1.1.1 or later.\nIf you are using a different SSL backend you can try setting TLS 1.3 cipher suites by\nusing the --proxy-ciphers option.\n\nIf --proxy-tls13-ciphers is provided several times, the last set value is used.\n\nExample:\ncurl --proxy-tls13-ciphers TLSAES128GCMSHA256 -x proxy https://example.com\n\nSee also --tls13-ciphers, --curves and --proxy-ciphers. Added in 7.61.0.\n", "long": "--proxy-tls13-ciphers" }, { "name": "--proxy-tlsauthtype ", "content": "Same as --tlsauthtype but used in HTTPS proxy context.\n\nIf --proxy-tlsauthtype is provided several times, the last set value is used.\n\nExample:\ncurl --proxy-tlsauthtype SRP -x https://proxy https://example.com\n\nSee also -x, --proxy and --proxy-tlsuser. Added in 7.52.0.\n", "long": "--proxy-tlsauthtype", "arg": "" }, { "name": "--proxy-tlspassword ", "content": "Same as --tlspassword but used in HTTPS proxy context.\n\nIf --proxy-tlspassword is provided several times, the last set value is used.\n\nExample:\ncurl --proxy-tlspassword passwd -x https://proxy https://example.com\n\nSee also -x, --proxy and --proxy-tlsuser. Added in 7.52.0.\n", "long": "--proxy-tlspassword", "arg": "" }, { "name": "--proxy-tlsuser ", "content": "Same as --tlsuser but used in HTTPS proxy context.\n\nIf --proxy-tlsuser is provided several times, the last set value is used.\n\nExample:\ncurl --proxy-tlsuser smith -x https://proxy https://example.com\n\nSee also -x, --proxy and --proxy-tlspassword. Added in 7.52.0.\n", "long": "--proxy-tlsuser", "arg": "" }, { "name": "--proxy-tlsv1", "content": "Same as -1, --tlsv1 but used in HTTPS proxy context.\n\nProviding --proxy-tlsv1 multiple times has no extra effect.\n\nExample:\ncurl --proxy-tlsv1 -x https://proxy https://example.com\n\nSee also -x, --proxy. Added in 7.52.0.\n", "long": "--proxy-tlsv1" }, { "name": "-U, --proxy-user ", "content": "Specify the user name and password to use for proxy authentication.\n\nIf you use a Windows SSPI-enabled curl binary and do either Negotiate or NTLM authen‐\ntication then you can tell curl to select the user name and password from your envi‐\nronment by specifying a single colon with this option: \"-U :\".\n\nOn systems where it works, curl hides the given option argument from process listings.\nThis is not enough to protect credentials from possibly getting seen by other users on\nthe same system as they still are visible for a moment before cleared. Such sensitive\ndata should be retrieved from a file instead or similar and never used in clear text\nin a command line.\n\nIf -U, --proxy-user is provided several times, the last set value is used.\n\nExample:\ncurl --proxy-user name:pwd -x proxy https://example.com\n\nSee also --proxy-pass.\n\n-x, --proxy [protocol://]host[:port]\nUse the specified proxy.\n\nThe proxy string can be specified with a protocol:// prefix. No protocol specified or\nhttp:// it is treated as an HTTP proxy. Use socks4://, socks4a://, socks5:// or\nsocks5h:// to request a specific SOCKS version to be used.\n\nUnix domain sockets are supported for socks proxy. Set localhost for the host part.\ne.g. socks5h://localhost/path/to/socket.sock\n\nHTTPS proxy support works set with the https:// protocol prefix for OpenSSL and GnuTLS\n(added in 7.52.0). It also works for BearSSL, mbedTLS, rustls, Schannel, Secure Trans‐\nport and wolfSSL (added in 7.87.0).\n\nUnrecognized and unsupported proxy protocols cause an error (added in 7.52.0). An‐\ncient curl versions ignored unknown schemes and used http:// instead.\n\nIf the port number is not specified in the proxy string, it is assumed to be 1080.\n\nThis option overrides existing environment variables that set the proxy to use. If\nthere is an environment variable setting a proxy, you can set proxy to \"\" to override\nit.\n\nAll operations that are performed over an HTTP proxy are transparently converted to\nHTTP. It means that certain protocol specific operations might not be available. This\nis not the case if you can tunnel through the proxy, as one with the -p, --proxytunnel\noption.\n\nUser and password that might be provided in the proxy string are URL decoded by curl.\nThis allows you to pass in special characters such as @ by using %40 or pass in a\ncolon with %3a.\n\nThe proxy host can be specified the same way as the proxy environment variables, in‐\ncluding the protocol prefix (http://) and the embedded user + password.\n\nWhen a proxy is used, the active FTP mode as set with -P, --ftp-port, cannot be used.\n\nIf -x, --proxy is provided several times, the last set value is used.\n\nExample:\ncurl --proxy http://proxy.example https://example.com\n\nSee also --socks5 and --proxy-basic.\n\n--proxy1.0 \nUse the specified HTTP 1.0 proxy. If the port number is not specified, it is assumed\nat port 1080.\n\nThe only difference between this and the HTTP proxy option -x, --proxy, is that at‐\ntempts to use CONNECT through the proxy specifies an HTTP 1.0 protocol instead of the\ndefault HTTP 1.1.\n\nProviding --proxy1.0 multiple times has no extra effect.\n\nExample:\ncurl --proxy1.0 -x http://proxy https://example.com\n\nSee also -x, --proxy, --socks5 and --preproxy.\n", "flag": "-U", "long": "--proxy-user", "arg": "" }, { "name": "-p, --proxytunnel", "content": "When an HTTP proxy is used -x, --proxy, this option makes curl tunnel the traffic\nthrough the proxy. The tunnel approach is made with the HTTP proxy CONNECT request and\nrequires that the proxy allows direct connect to the remote port number curl wants to\ntunnel through to.\n\nTo suppress proxy CONNECT response headers when curl is set to output headers use\n--suppress-connect-headers.\n\nProviding -p, --proxytunnel multiple times has no extra effect. Disable it again with\n--no-proxytunnel.\n\nExample:\ncurl --proxytunnel -x http://proxy https://example.com\n\nSee also -x, --proxy.\n", "flag": "-p", "long": "--proxytunnel" }, { "name": "--pubkey ", "content": "(SFTP SCP) Public key file name. Allows you to provide your public key in this sepa‐\nrate file.\n\ncurl attempts to automatically extract the public key from the private key file, so\npassing this option is generally not required. Note that this public key extraction\nrequires libcurl to be linked against a copy of libssh2 1.2.8 or higher that is itself\nlinked against OpenSSL.\n\nIf --pubkey is provided several times, the last set value is used.\n\nExample:\ncurl --pubkey file.pub sftp://example.com/\n\nSee also --pass.\n", "long": "--pubkey", "arg": "" }, { "name": "-Q, --quote ", "content": "(FTP SFTP) Send an arbitrary command to the remote FTP or SFTP server. Quote commands\nare sent BEFORE the transfer takes place (just after the initial PWD command in an FTP\ntransfer, to be exact). To make commands take place after a successful transfer, pre‐\nfix them with a dash '-'.\n\n(FTP only) To make commands be sent after curl has changed the working directory, just\nbefore the file transfer command(s), prefix the command with a '+'. This is not per‐\nformed when a directory listing is performed.\n\nYou may specify any number of commands.\n\nBy default curl stops at first failure. To make curl continue even if the command\nfails, prefix the command with an asterisk (*). Otherwise, if the server returns fail‐\nure for one of the commands, the entire operation is aborted.\n\nYou must send syntactically correct FTP commands as RFC 959 defines to FTP servers, or\none of the commands listed below to SFTP servers.\n\nSFTP is a binary protocol. Unlike for FTP, curl interprets SFTP quote commands itself\nbefore sending them to the server. File names may be quoted shell-style to embed\nspaces or special characters. Following is the list of all supported SFTP quote com‐\nmands:\n\n\"atime date file\"\nThe atime command sets the last access time of the file named by the file\noperand. The can be all sorts of date strings, see the\ncurlgetdate(3) man page for date expression details. (Added in 7.73.0)\n\n\"chgrp group file\"\nThe chgrp command sets the group ID of the file named by the file operand to\nthe group ID specified by the group operand. The group operand is a decimal in‐\nteger group ID.\n\n\"chmod mode file\"\nThe chmod command modifies the file mode bits of the specified file. The mode\noperand is an octal integer mode number.\n\n\"chown user file\"\nThe chown command sets the owner of the file named by the file operand to the\nuser ID specified by the user operand. The user operand is a decimal integer\nuser ID.\n\n\"ln sourcefile targetfile\"\nThe ln and symlink commands create a symbolic link at the targetfile location\npointing to the sourcefile location.\n\n\"mkdir directoryname\"\nThe mkdir command creates the directory named by the directoryname operand.\n\n\"mtime date file\"\nThe mtime command sets the last modification time of the file named by the file\noperand. The can be all sorts of date strings, see the\ncurlgetdate(3) man page for date expression details. (Added in 7.73.0)\n\n\"pwd\" The pwd command returns the absolute path name of the current working direc‐\ntory.\n\n\"rename source target\"\nThe rename command renames the file or directory named by the source operand to\nthe destination path named by the target operand.\n\n\"rm file\"\nThe rm command removes the file specified by the file operand.\n\n\"rmdir directory\"\nThe rmdir command removes the directory entry specified by the directory\noperand, provided it is empty.\n\n\"symlink sourcefile targetfile\"\nSee ln.\n\n-Q, --quote can be used several times in a command line\n\nExample:\ncurl --quote \"DELE file\" ftp://example.com/foo\n\nSee also -X, --request.\n", "flag": "-Q", "long": "--quote", "arg": "" }, { "name": "--random-file ", "content": "Deprecated option. This option is ignored (added in 7.84.0). Prior to that it only had\nan effect on curl if built to use old versions of OpenSSL.\n\nSpecify the path name to file containing random data. The data may be used to seed the\nrandom engine for SSL connections.\n\nIf --random-file is provided several times, the last set value is used.\n\nExample:\ncurl --random-file rubbish https://example.com\n\nSee also --egd-file.\n", "long": "--random-file", "arg": "" }, { "name": "-r, --range ", "content": "(HTTP FTP SFTP FILE) Retrieve a byte range (i.e. a partial document) from an HTTP/1.1,\nFTP or SFTP server or a local FILE. Ranges can be specified in a number of ways.\n\n0-499 specifies the first 500 bytes\n\n500-999 specifies the second 500 bytes\n\n-500 specifies the last 500 bytes\n\n9500- specifies the bytes from offset 9500 and forward\n\n0-0,-1 specifies the first and last byte only(*)(HTTP)\n\n100-199,500-599\nspecifies two separate 100-byte ranges(*) (HTTP)\n\n(*) = NOTE that this causes the server to reply with a multipart response, which is\nreturned as-is by curl! Parsing or otherwise transforming this response is the respon‐\nsibility of the caller.\n\nOnly digit characters (0-9) are valid in the 'start' and 'stop' fields of the\n'start-stop' range syntax. If a non-digit character is given in the range, the\nserver's response is unspecified, depending on the server's configuration.\n\nMany HTTP/1.1 servers do not have this feature enabled, so that when you attempt to\nget a range, curl instead gets the whole document.\n\nFTP and SFTP range downloads only support the simple 'start-stop' syntax (optionally\nwith one of the numbers omitted). FTP use depends on the extended FTP command SIZE.\n\nIf -r, --range is provided several times, the last set value is used.\n\nExample:\ncurl --range 22-44 https://example.com\n\nSee also -C, --continue-at and -a, --append.\n", "flag": "-r", "long": "--range", "arg": "" }, { "name": "--rate ", "content": "Specify the maximum transfer frequency you allow curl to use - in number of transfer\nstarts per time unit (sometimes called request rate). Without this option, curl starts\nthe next transfer as fast as possible.\n\nIf given several URLs and a transfer completes faster than the allowed rate, curl\nwaits until the next transfer is started to maintain the requested rate. This option\nhas no effect when -Z, --parallel is used.\n\nThe request rate is provided as \"N/U\" where N is an integer number and U is a time\nunit. Supported units are 's' (second), 'm' (minute), 'h' (hour) and 'd' /(day, as in\na 24 hour unit). The default time unit, if no \"/U\" is provided, is number of transfers\nper hour.\n\nIf curl is told to allow 10 requests per minute, it does not start the next request\nuntil 6 seconds have elapsed since the previous transfer was started.\n\nThis function uses millisecond resolution. If the allowed frequency is set more than\n1000 per second, it instead runs unrestricted.\n\nWhen retrying transfers, enabled with --retry, the separate retry delay logic is used\nand not this setting.\n\nThis option is global and does not need to be specified for each use of --next.\n\nIf --rate is provided several times, the last set value is used.\n\nExamples:\ncurl --rate 2/s https://example.com ...\ncurl --rate 3/h https://example.com ...\ncurl --rate 14/m https://example.com ...\n\nSee also --limit-rate and --retry-delay. Added in 7.84.0.\n\n--raw (HTTP) When used, it disables all internal HTTP decoding of content or transfer encod‐\nings and instead makes them passed on unaltered, raw.\n\nProviding --raw multiple times has no extra effect. Disable it again with --no-raw.\n\nExample:\ncurl --raw https://example.com\n\nSee also --tr-encoding.\n", "long": "--rate" }, { "name": "-e, --referer ", "content": "(HTTP) Sends the \"Referrer Page\" information to the HTTP server. This can also be set\nwith the -H, --header flag of course. When used with -L, --location you can append\n\";auto\" to the -e, --referer URL to make curl automatically set the previous URL when\nit follows a Location: header. The \";auto\" string can be used alone, even if you do\nnot set an initial -e, --referer.\n\nIf -e, --referer is provided several times, the last set value is used.\n\nExamples:\ncurl --referer \"https://fake.example\" https://example.com\ncurl --referer \"https://fake.example;auto\" -L https://example.com\ncurl --referer \";auto\" -L https://example.com\n\nSee also -A, --user-agent and -H, --header.\n", "flag": "-e", "long": "--referer", "arg": "" }, { "name": "-J, --remote-header-name", "content": "(HTTP) This option tells the -O, --remote-name option to use the server-specified Con‐\ntent-Disposition filename instead of extracting a filename from the URL. If the\nserver-provided file name contains a path, that is stripped off before the file name\nis used.\n\nThe file is saved in the current directory, or in the directory specified with --out‐\nput-dir.\n\nIf the server specifies a file name and a file with that name already exists in the\ndestination directory, it is not overwritten and an error occurs - unless you allow it\nby using the --clobber option. If the server does not specify a file name then this\noption has no effect.\n\nThere is no attempt to decode %-sequences (yet) in the provided file name, so this op‐\ntion may provide you with rather unexpected file names.\n\nThis feature uses the name from the \"filename\" field, it does not yet support the\n\"filename*\" field (filenames with explicit character sets).\n\nWARNING: Exercise judicious use of this option, especially on Windows. A rogue server\ncould send you the name of a DLL or other file that could be loaded automatically by\nWindows or some third party software.\n\nProviding -J, --remote-header-name multiple times has no extra effect. Disable it\nagain with --no-remote-header-name.\n\nExample:\ncurl -OJ https://example.com/file\n\nSee also -O, --remote-name.\n", "flag": "-J", "long": "--remote-header-name" }, { "name": "--remote-name-all", "content": "This option changes the default action for all given URLs to be dealt with as if -O,\n--remote-name were used for each one. So if you want to disable that for a specific\nURL after --remote-name-all has been used, you must use \"-o -\" or --no-remote-name.\n\nProviding --remote-name-all multiple times has no extra effect. Disable it again with\n--no-remote-name-all.\n\nExample:\ncurl --remote-name-all ftp://example.com/file1 ftp://example.com/file2\n\nSee also -O, --remote-name.\n", "long": "--remote-name-all" }, { "name": "-O, --remote-name", "content": "Write output to a local file named like the remote file we get. (Only the file part of\nthe remote file is used, the path is cut off.)\n\nThe file is saved in the current working directory. If you want the file saved in a\ndifferent directory, make sure you change the current working directory before invok‐\ning curl with this option or use --output-dir.\n\nThe remote file name to use for saving is extracted from the given URL, nothing else,\nand if it already exists it is overwritten. If you want the server to be able to\nchoose the file name refer to -J, --remote-header-name which can be used in addition\nto this option. If the server chooses a file name and that name already exists it is\nnot overwritten.\n\nThere is no URL decoding done on the file name. If it has %20 or other URL encoded\nparts of the name, they end up as-is as file name.\n\nYou may use this option as many times as the number of URLs you have.\n\n-O, --remote-name can be used several times in a command line\n\nExample:\ncurl -O https://example.com/filename\n\nSee also --remote-name-all, --output-dir and -J, --remote-header-name.\n", "flag": "-O", "long": "--remote-name" }, { "name": "-R, --remote-time", "content": "Makes curl attempt to figure out the timestamp of the remote file that is getting\ndownloaded, and if that is available make the local file get that same timestamp.\n\nProviding -R, --remote-time multiple times has no extra effect. Disable it again with\n--no-remote-time.\n\nExample:\ncurl --remote-time -o foo https://example.com\n\nSee also -O, --remote-name and -z, --time-cond.\n", "flag": "-R", "long": "--remote-time" }, { "name": "--remove-on-error", "content": "When curl returns an error when told to save output in a local file, this option re‐\nmoves that saved file before exiting. This prevents curl from leaving a partial file\nin the case of an error during transfer.\n\nIf the output is not a file, this option has no effect.\n\nProviding --remove-on-error multiple times has no extra effect. Disable it again with\n--no-remove-on-error.\n\nExample:\ncurl --remove-on-error -o output https://example.com\n\nSee also -f, --fail. Added in 7.83.0.\n", "long": "--remove-on-error" }, { "name": "--request-target ", "content": "(HTTP) Tells curl to use an alternative \"target\" (path) instead of using the path as\nprovided in the URL. Particularly useful when wanting to issue HTTP requests without\nleading slash or other data that does not follow the regular URL pattern, like \"OP‐\nTIONS *\".\n\ncurl passes on the verbatim string you give it its the request without any filter or\nother safe guards. That includes white space and control characters.\n\nIf --request-target is provided several times, the last set value is used.\n\nExample:\ncurl --request-target \"*\" -X OPTIONS https://example.com\n\nSee also -X, --request. Added in 7.55.0.\n", "long": "--request-target", "arg": "" }, { "name": "-X, --request ", "content": "Change the method to use when starting the transfer.\n\ncurl passes on the verbatim string you give it its the request without any filter or\nother safe guards. That includes white space and control characters.\n\nHTTP Specifies a custom request method to use when communicating with the\nHTTP server. The specified request method is used instead of the method\notherwise used (which defaults to GET). Read the HTTP 1.1 specification\nfor details and explanations. Common additional HTTP requests include\nPUT and DELETE, but related technologies like WebDAV offers PROPFIND,\nCOPY, MOVE and more.\n\nNormally you do not need this option. All sorts of GET, HEAD, POST and\nPUT requests are rather invoked by using dedicated command line op‐\ntions.\n\nThis option only changes the actual word used in the HTTP request, it\ndoes not alter the way curl behaves. So for example if you want to make\na proper HEAD request, using -X HEAD does not suffice. You need to use\nthe -I, --head option.\n\nThe method string you set with -X, --request is used for all requests,\nwhich if you for example use -L, --location may cause unintended\nside-effects when curl does not change request method according to the\nHTTP 30x response codes - and similar.\n\nFTP Specifies a custom FTP command to use instead of LIST when doing file\nlists with FTP.\n\nPOP3 Specifies a custom POP3 command to use instead of LIST or RETR.\n\n\nIMAP Specifies a custom IMAP command to use instead of LIST.\n\nSMTP Specifies a custom SMTP command to use instead of HELP or VRFY.\n\nIf -X, --request is provided several times, the last set value is used.\n\nExamples:\ncurl -X \"DELETE\" https://example.com\ncurl -X NLST ftp://example.com/\n\nSee also --request-target.\n\n--resolve <[+]host:port:addr[,addr]...>\nProvide a custom address for a specific host and port pair. Using this, you can make\nthe curl requests(s) use a specified address and prevent the otherwise normally re‐\nsolved address to be used. Consider it a sort of /etc/hosts alternative provided on\nthe command line. The port number should be the number used for the specific protocol\nthe host is used for. It means you need several entries if you want to provide address\nfor the same host but different ports.\n\nBy specifying '*' as host you can tell curl to resolve any host and specific port pair\nto the specified address. Wildcard is resolved last so any --resolve with a specific\nhost and port is used first.\n\nThe provided address set by this option is used even if -4, --ipv4 or -6, --ipv6 is\nset to make curl use another IP version.\n\nBy prefixing the host with a '+' you can make the entry time out after curl's default\ntimeout (1 minute). Note that this only makes sense for long running parallel trans‐\nfers with a lot of files. In such cases, if this option is used curl tries to resolve\nthe host as it normally would once the timeout has expired.\n\nSupport for providing the IP address within [brackets] was added in 7.57.0.\n\nSupport for providing multiple IP addresses per entry was added in 7.59.0.\n\nSupport for resolving with wildcard was added in 7.64.0.\n\nSupport for the '+' prefix was was added in 7.75.0.\n\n--resolve can be used several times in a command line\n\nExample:\ncurl --resolve example.com:443:127.0.0.1 https://example.com\n\nSee also --connect-to and --alt-svc.\n", "flag": "-X", "long": "--request", "arg": "" }, { "name": "--retry-all-errors", "content": "Retry on any error. This option is used together with --retry.\n\nThis option is the \"sledgehammer\" of retrying. Do not use this option by default (for\nexample in your curlrc), there may be unintended consequences such as sending or re‐\nceiving duplicate data. Do not use with redirected input or output. You'd be much bet‐\nter off handling your unique problems in shell script. Please read the example below.\n\nWARNING: For server compatibility curl attempts to retry failed flaky transfers as\nclose as possible to how they were started, but this is not possible with redirected\ninput or output. For example, before retrying it removes output data from a failed\npartial transfer that was written to an output file. However this is not true of data\nredirected to a | pipe or > file, which are not reset. We strongly suggest you do not\nparse or record output via redirect in combination with this option, since you may re‐\nceive duplicate data.\n\nBy default curl does not return error for transfers with an HTTP response code that\nindicates an HTTP error, if the transfer was successful. For example, if a server\nreplies 404 Not Found and the reply is fully received then that is not an error. When\n--retry is used then curl retries on some HTTP response codes that indicate transient\nHTTP errors, but that does not include most 4xx response codes such as 404. If you\nwant to retry on all response codes that indicate HTTP errors (4xx and 5xx) then com‐\nbine with -f, --fail.\n\nProviding --retry-all-errors multiple times has no extra effect. Disable it again\nwith --no-retry-all-errors.\n\nExample:\ncurl --retry 5 --retry-all-errors https://example.com\n\nSee also --retry. Added in 7.71.0.\n", "long": "--retry-all-errors" }, { "name": "--retry-connrefused", "content": "In addition to the other conditions, consider ECONNREFUSED as a transient error too\nfor --retry. This option is used together with --retry.\n\nProviding --retry-connrefused multiple times has no extra effect. Disable it again\nwith --no-retry-connrefused.\n\nExample:\ncurl --retry-connrefused --retry 7 https://example.com\n\nSee also --retry and --retry-all-errors. Added in 7.52.0.\n", "long": "--retry-connrefused" }, { "name": "--retry-delay ", "content": "Make curl sleep this amount of time before each retry when a transfer has failed with\na transient error (it changes the default backoff time algorithm between retries).\nThis option is only interesting if --retry is also used. Setting this delay to zero\nmakes curl use the default backoff time.\n\nIf --retry-delay is provided several times, the last set value is used.\n\nExample:\ncurl --retry-delay 5 --retry 7 https://example.com\n\nSee also --retry.\n", "long": "--retry-delay", "arg": "" }, { "name": "--retry-max-time ", "content": "The retry timer is reset before the first transfer attempt. Retries are done as usual\n(see --retry) as long as the timer has not reached this given limit. Notice that if\nthe timer has not reached the limit, the request is made and while performing, it may\ntake longer than this given time period. To limit a single request's maximum time, use\n-m, --max-time. Set this option to zero to not timeout retries.\n\nIf --retry-max-time is provided several times, the last set value is used.\n\nExample:\ncurl --retry-max-time 30 --retry 10 https://example.com\n\nSee also --retry.\n", "long": "--retry-max-time", "arg": "" }, { "name": "--retry ", "content": "If a transient error is returned when curl tries to perform a transfer, it retries\nthis number of times before giving up. Setting the number to 0 makes curl do no re‐\ntries (which is the default). Transient error means either: a timeout, an FTP 4xx re‐\nsponse code or an HTTP 408, 429, 500, 502, 503 or 504 response code.\n\nWhen curl is about to retry a transfer, it first waits one second and then for all\nforthcoming retries it doubles the waiting time until it reaches 10 minutes which then\nremains delay between the rest of the retries. By using --retry-delay you disable this\nexponential backoff algorithm. See also --retry-max-time to limit the total time al‐\nlowed for retries.\n\ncurl complies with the Retry-After: response header if one was present to know when to\nissue the next retry (added in 7.66.0).\n\nIf --retry is provided several times, the last set value is used.\n\nExample:\ncurl --retry 7 https://example.com\n\nSee also --retry-max-time.\n", "long": "--retry", "arg": "" }, { "name": "--sasl-authzid ", "content": "Use this authorization identity (authzid), during SASL PLAIN authentication, in addi‐\ntion to the authentication identity (authcid) as specified by -u, --user.\n\nIf the option is not specified, the server derives the authzid from the authcid, but\nif specified, and depending on the server implementation, it may be used to access an‐\nother user's inbox, that the user has been granted access to, or a shared mailbox for\nexample.\n\nIf --sasl-authzid is provided several times, the last set value is used.\n\nExample:\ncurl --sasl-authzid zid imap://example.com/\n\nSee also --login-options. Added in 7.66.0.\n", "long": "--sasl-authzid", "arg": "" }, { "name": "--sasl-ir", "content": "Enable initial response in SASL authentication.\n\nProviding --sasl-ir multiple times has no extra effect. Disable it again with\n--no-sasl-ir.\n\nExample:\ncurl --sasl-ir imap://example.com/\n\nSee also --sasl-authzid.\n", "long": "--sasl-ir" }, { "name": "--service-name ", "content": "This option allows you to change the service name for SPNEGO.\n\nIf --service-name is provided several times, the last set value is used.\n\nExample:\ncurl --service-name sockd/server https://example.com\n\nSee also --negotiate and --proxy-service-name.\n", "long": "--service-name", "arg": "" }, { "name": "-S, --show-error", "content": "When used with -s, --silent, it makes curl show an error message if it fails.\n\nThis option is global and does not need to be specified for each use of --next.\n\nProviding -S, --show-error multiple times has no extra effect. Disable it again with\n--no-show-error.\n\nExample:\ncurl --show-error --silent https://example.com\n\nSee also --no-progress-meter.\n", "flag": "-S", "long": "--show-error" }, { "name": "-s, --silent", "content": "Silent or quiet mode. Do not show progress meter or error messages. Makes Curl mute.\nIt still outputs the data you ask for, potentially even to the terminal/stdout unless\nyou redirect it.\n\nUse -S, --show-error in addition to this option to disable progress meter but still\nshow error messages.\n\nProviding -s, --silent multiple times has no extra effect. Disable it again with\n--no-silent.\n\nExample:\ncurl -s https://example.com\n\nSee also -v, --verbose, --stderr and --no-progress-meter.\n\n--socks4 \nUse the specified SOCKS4 proxy. If the port number is not specified, it is assumed at\nport 1080. Using this socket type make curl resolve the host name and passing the ad‐\ndress on to the proxy.\n\nTo specify proxy on a unix domain socket, use localhost for host, e.g. socks4://lo‐\ncalhost/path/to/socket.sock\n\nThis option overrides any previous use of -x, --proxy, as they are mutually exclusive.\n\nThis option is superfluous since you can specify a socks4 proxy with -x, --proxy using\na socks4:// protocol prefix.\n\n--preproxy can be used to specify a SOCKS proxy at the same time proxy is used with an\nHTTP/HTTPS proxy (added in 7.52.0). In such a case, curl first connects to the SOCKS\nproxy and then connects (through SOCKS) to the HTTP or HTTPS proxy.\n\nIf --socks4 is provided several times, the last set value is used.\n\nExample:\ncurl --socks4 hostname:4096 https://example.com\n\nSee also --socks4a, --socks5 and --socks5-hostname.\n\n--socks4a \nUse the specified SOCKS4a proxy. If the port number is not specified, it is assumed at\nport 1080. This asks the proxy to resolve the host name.\n\nTo specify proxy on a unix domain socket, use localhost for host, e.g. socks4a://lo‐\ncalhost/path/to/socket.sock\n\nThis option overrides any previous use of -x, --proxy, as they are mutually exclusive.\n\nThis option is superfluous since you can specify a socks4a proxy with -x, --proxy us‐\ning a socks4a:// protocol prefix.\n\n--preproxy can be used to specify a SOCKS proxy at the same time -x, --proxy is used\nwith an HTTP/HTTPS proxy (added in 7.52.0). In such a case, curl first connects to the\nSOCKS proxy and then connects (through SOCKS) to the HTTP or HTTPS proxy.\n\nIf --socks4a is provided several times, the last set value is used.\n\nExample:\ncurl --socks4a hostname:4096 https://example.com\n\nSee also --socks4, --socks5 and --socks5-hostname.\n", "flag": "-s", "long": "--silent" }, { "name": "--socks5-basic", "content": "Tells curl to use username/password authentication when connecting to a SOCKS5 proxy.\nThe username/password authentication is enabled by default. Use --socks5-gssapi to\nforce GSS-API authentication to SOCKS5 proxies.\n\nProviding --socks5-basic multiple times has no extra effect.\n\nExample:\ncurl --socks5-basic --socks5 hostname:4096 https://example.com\n\nSee also --socks5. Added in 7.55.0.\n", "long": "--socks5-basic" }, { "name": "--socks5-gssapi-nec", "content": "As part of the GSS-API negotiation a protection mode is negotiated. RFC 1961 says in\nsection 4.3/4.4 it should be protected, but the NEC reference implementation does not.\nThe option --socks5-gssapi-nec allows the unprotected exchange of the protection mode\nnegotiation.\n\nProviding --socks5-gssapi-nec multiple times has no extra effect. Disable it again\nwith --no-socks5-gssapi-nec.\n\nExample:\ncurl --socks5-gssapi-nec --socks5 hostname:4096 https://example.com\n\nSee also --socks5.\n", "long": "--socks5-gssapi-nec" }, { "name": "--socks5-gssapi-service ", "content": "The default service name for a socks server is rcmd/server-fqdn. This option allows\nyou to change it.\n\nIf --socks5-gssapi-service is provided several times, the last set value is used.\n\nExample:\ncurl --socks5-gssapi-service sockd --socks5 hostname:4096 https://example.com\n\nSee also --socks5.\n", "long": "--socks5-gssapi-service", "arg": "" }, { "name": "--socks5-gssapi", "content": "Tells curl to use GSS-API authentication when connecting to a SOCKS5 proxy. The\nGSS-API authentication is enabled by default (if curl is compiled with GSS-API sup‐\nport). Use --socks5-basic to force username/password authentication to SOCKS5 prox‐\nies.\n\nProviding --socks5-gssapi multiple times has no extra effect. Disable it again with\n--no-socks5-gssapi.\n\nExample:\ncurl --socks5-gssapi --socks5 hostname:4096 https://example.com\n\nSee also --socks5. Added in 7.55.0.\n\n--socks5-hostname \nUse the specified SOCKS5 proxy (and let the proxy resolve the host name). If the port\nnumber is not specified, it is assumed at port 1080.\n\nTo specify proxy on a unix domain socket, use localhost for host, e.g. socks5h://lo‐\ncalhost/path/to/socket.sock\n\nThis option overrides any previous use of -x, --proxy, as they are mutually exclusive.\n\nThis option is superfluous since you can specify a socks5 hostname proxy with -x,\n--proxy using a socks5h:// protocol prefix.\n\n--preproxy can be used to specify a SOCKS proxy at the same time -x, --proxy is used\nwith an HTTP/HTTPS proxy (added in 7.52.0). In such a case, curl first connects to the\nSOCKS proxy and then connects (through SOCKS) to the HTTP or HTTPS proxy.\n\nIf --socks5-hostname is provided several times, the last set value is used.\n\nExample:\ncurl --socks5-hostname proxy.example:7000 https://example.com\n\nSee also --socks5 and --socks4a.\n\n--socks5 \nUse the specified SOCKS5 proxy - but resolve the host name locally. If the port number\nis not specified, it is assumed at port 1080.\n\nTo specify proxy on a unix domain socket, use localhost for host, e.g. socks5://lo‐\ncalhost/path/to/socket.sock\n\nThis option overrides any previous use of -x, --proxy, as they are mutually exclusive.\n\nThis option is superfluous since you can specify a socks5 proxy with -x, --proxy using\na socks5:// protocol prefix.\n\n--preproxy can be used to specify a SOCKS proxy at the same time -x, --proxy is used\nwith an HTTP/HTTPS proxy (added in 7.52.0). In such a case, curl first connects to the\nSOCKS proxy and then connects (through SOCKS) to the HTTP or HTTPS proxy.\n\nThis option (as well as --socks4) does not work with IPV6, FTPS or LDAP.\n\nIf --socks5 is provided several times, the last set value is used.\n\nExample:\ncurl --socks5 proxy.example:7000 https://example.com\n\nSee also --socks5-hostname and --socks4a.\n", "long": "--socks5-gssapi" }, { "name": "-Y, --speed-limit ", "content": "If a transfer is slower than this given speed (in bytes per second) for speed-time\nseconds it gets aborted. speed-time is set with -y, --speed-time and is 30 if not set.\n\nIf -Y, --speed-limit is provided several times, the last set value is used.\n\nExample:\ncurl --speed-limit 300 --speed-time 10 https://example.com\n\nSee also -y, --speed-time, --limit-rate and -m, --max-time.\n", "flag": "-Y", "long": "--speed-limit", "arg": "" }, { "name": "-y, --speed-time ", "content": "If a transfer runs slower than speed-limit bytes per second during a speed-time pe‐\nriod, the transfer is aborted. If speed-time is used, the default speed-limit is 1 un‐\nless set with -Y, --speed-limit.\n\nThis option controls transfers (in both directions) but does not affect slow connects\netc. If this is a concern for you, try the --connect-timeout option.\n\nIf -y, --speed-time is provided several times, the last set value is used.\n\nExample:\ncurl --speed-limit 300 --speed-time 10 https://example.com\n\nSee also -Y, --speed-limit and --limit-rate.\n", "flag": "-y", "long": "--speed-time", "arg": "" }, { "name": "--ssl-allow-beast", "content": "This option tells curl to not work around a security flaw in the SSL3 and TLS1.0 pro‐\ntocols known as BEAST. If this option is not used, the SSL layer may use workarounds\nknown to cause interoperability problems with some older SSL implementations.\n\nWARNING: this option loosens the SSL security, and by using this flag you ask for ex‐\nactly that.\n\nProviding --ssl-allow-beast multiple times has no extra effect. Disable it again with\n--no-ssl-allow-beast.\n\nExample:\ncurl --ssl-allow-beast https://example.com\n\nSee also --proxy-ssl-allow-beast and -k, --insecure.\n", "long": "--ssl-allow-beast" }, { "name": "--ssl-auto-client-cert", "content": "(Schannel) Tell libcurl to automatically locate and use a client certificate for au‐\nthentication, when requested by the server. Since the server can request any certifi‐\ncate that supports client authentication in the OS certificate store it could be a\nprivacy violation and unexpected.\n\nProviding --ssl-auto-client-cert multiple times has no extra effect. Disable it again\nwith --no-ssl-auto-client-cert.\n\nExample:\ncurl --ssl-auto-client-cert https://example.com\n\nSee also --proxy-ssl-auto-client-cert. Added in 7.77.0.\n", "long": "--ssl-auto-client-cert" }, { "name": "--ssl-no-revoke", "content": "(Schannel) This option tells curl to disable certificate revocation checks. WARNING:\nthis option loosens the SSL security, and by using this flag you ask for exactly that.\n\nProviding --ssl-no-revoke multiple times has no extra effect. Disable it again with\n--no-ssl-no-revoke.\n\nExample:\ncurl --ssl-no-revoke https://example.com\n\nSee also --crlfile.\n", "long": "--ssl-no-revoke" }, { "name": "--ssl-reqd", "content": "(FTP IMAP POP3 SMTP LDAP) Require SSL/TLS for the connection. Terminates the connec‐\ntion if the transfer cannot be upgraded to use SSL/TLS.\n\nThis option is handled in LDAP (added in 7.81.0). It is fully supported by the OpenL‐\nDAP backend and rejected by the generic ldap backend if explicit TLS is required.\n\nThis option is unnecessary if you use a URL scheme that in itself implies immediate\nand implicit use of TLS, like for FTPS, IMAPS, POP3S, SMTPS and LDAPS. Such a transfer\nalways fails if the TLS handshake does not work.\n\nThis option was formerly known as --ftp-ssl-reqd.\n\nProviding --ssl-reqd multiple times has no extra effect. Disable it again with\n--no-ssl-reqd.\n\nExample:\ncurl --ssl-reqd ftp://example.com\n\nSee also --ssl and -k, --insecure.\n", "long": "--ssl-reqd" }, { "name": "--ssl-revoke-best-effort", "content": "(Schannel) This option tells curl to ignore certificate revocation checks when they\nfailed due to missing/offline distribution points for the revocation check lists.\n\nProviding --ssl-revoke-best-effort multiple times has no extra effect. Disable it\nagain with --no-ssl-revoke-best-effort.\n\nExample:\ncurl --ssl-revoke-best-effort https://example.com\n\nSee also --crlfile and -k, --insecure. Added in 7.70.0.\n\n--ssl (FTP IMAP POP3 SMTP LDAP) Warning: this is considered an insecure option. Consider us‐\ning --ssl-reqd instead to be sure curl upgrades to a secure connection.\n\nTry to use SSL/TLS for the connection. Reverts to a non-secure connection if the\nserver does not support SSL/TLS. See also --ftp-ssl-control and --ssl-reqd for differ‐\nent levels of encryption required.\n\nThis option is handled in LDAP (added in 7.81.0). It is fully supported by the OpenL‐\nDAP backend and ignored by the generic ldap backend.\n\nPlease note that a server may close the connection if the negotiation does not suc‐\nceed.\n\nThis option was formerly known as --ftp-ssl. That option name can still be used but\nmight be removed in a future version.\n\nProviding --ssl multiple times has no extra effect. Disable it again with --no-ssl.\n\nExample:\ncurl --ssl pop3://example.com/\n\nSee also --ssl-reqd, -k, --insecure and --ciphers.\n\n-2, --sslv2\n(SSL) This option previously asked curl to use SSLv2, but is now ignored (added in\n7.77.0). SSLv2 is widely considered insecure (see RFC 6176).\n\nProviding -2, --sslv2 multiple times has no extra effect.\n\nExample:\ncurl --sslv2 https://example.com\n\nSee also --http1.1 and --http2. -2, --sslv2 requires that the underlying libcurl was\nbuilt to support TLS. This option is mutually exclusive to -3, --sslv3 and -1, --tlsv1\nand --tlsv1.1 and --tlsv1.2.\n\n-3, --sslv3\n(SSL) This option previously asked curl to use SSLv3, but is now ignored (added in\n7.77.0). SSLv3 is widely considered insecure (see RFC 7568).\n\nProviding -3, --sslv3 multiple times has no extra effect.\n\nExample:\ncurl --sslv3 https://example.com\n\nSee also --http1.1 and --http2. -3, --sslv3 requires that the underlying libcurl was\nbuilt to support TLS. This option is mutually exclusive to -2, --sslv2 and -1, --tlsv1\nand --tlsv1.1 and --tlsv1.2.\n", "long": "--ssl-revoke-best-effort" }, { "name": "--stderr ", "content": "Redirect all writes to stderr to the specified file instead. If the file name is a\nplain '-', it is instead written to stdout.\n\nThis option is global and does not need to be specified for each use of --next.\n\nIf --stderr is provided several times, the last set value is used.\n\nExample:\ncurl --stderr output.txt https://example.com\n\nSee also -v, --verbose and -s, --silent.\n", "long": "--stderr", "arg": "" }, { "name": "--styled-output", "content": "Enables the automatic use of bold font styles when writing HTTP headers to the termi‐\nnal. Use --no-styled-output to switch them off.\n\nStyled output requires a terminal that supports bold fonts. This feature is not\npresent on curl for Windows due to lack of this capability.\n\nThis option is global and does not need to be specified for each use of --next.\n\nProviding --styled-output multiple times has no extra effect. Disable it again with\n--no-styled-output.\n\nExample:\ncurl --styled-output -I https://example.com\n\nSee also -I, --head and -v, --verbose. Added in 7.61.0.\n", "long": "--styled-output" }, { "name": "--suppress-connect-headers", "content": "When -p, --proxytunnel is used and a CONNECT request is made do not output proxy CON‐\nNECT response headers. This option is meant to be used with -D, --dump-header or -i,\n--include which are used to show protocol headers in the output. It has no effect on\ndebug options such as -v, --verbose or --trace, or any statistics.\n\nProviding --suppress-connect-headers multiple times has no extra effect. Disable it\nagain with --no-suppress-connect-headers.\n\nExample:\ncurl --suppress-connect-headers --include -x proxy https://example.com\n\nSee also -D, --dump-header, -i, --include and -p, --proxytunnel. Added in 7.54.0.\n", "long": "--suppress-connect-headers" }, { "name": "--tcp-fastopen", "content": "Enable use of TCP Fast Open (RFC 7413). TCP Fast Open is a TCP extension that allows\ndata to get sent earlier over the connection (before the final handshake ACK) if the\nclient and server have been connected previously.\n\nProviding --tcp-fastopen multiple times has no extra effect. Disable it again with\n--no-tcp-fastopen.\n\nExample:\ncurl --tcp-fastopen https://example.com\n\nSee also --false-start.\n", "long": "--tcp-fastopen" }, { "name": "--tcp-nodelay", "content": "Turn on the TCPNODELAY option. See the curleasysetopt(3) man page for details about\nthis option.\n\ncurl sets this option by default and you need to explicitly switch it off if you do\nnot want it on (added in 7.50.2).\n\nProviding --tcp-nodelay multiple times has no extra effect. Disable it again with\n--no-tcp-nodelay.\n\nExample:\ncurl --tcp-nodelay https://example.com\n\nSee also -N, --no-buffer.\n", "long": "--tcp-nodelay" }, { "name": "-t, --telnet-option ", "content": "Pass options to the telnet protocol. Supported options are:\n\n\nTTYPE= Sets the terminal type.\n\nXDISPLOC= Sets the X display location.\n\nNEWENV= Sets an environment variable.\n\n-t, --telnet-option can be used several times in a command line\n\nExample:\ncurl -t TTYPE=vt100 telnet://example.com/\n\nSee also -K, --config.\n", "flag": "-t", "long": "--telnet-option", "arg": "" }, { "name": "--tftp-blksize ", "content": "(TFTP) Set the TFTP BLKSIZE option (must be >512). This is the block size that curl\ntries to use when transferring data to or from a TFTP server. By default 512 bytes are\nused.\n\nIf --tftp-blksize is provided several times, the last set value is used.\n\nExample:\ncurl --tftp-blksize 1024 tftp://example.com/file\n\nSee also --tftp-no-options.\n", "long": "--tftp-blksize", "arg": "" }, { "name": "--tftp-no-options", "content": "(TFTP) Tells curl not to send TFTP options requests.\n\nThis option improves interop with some legacy servers that do not acknowledge or prop‐\nerly implement TFTP options. When this option is used --tftp-blksize is ignored.\n\nProviding --tftp-no-options multiple times has no extra effect. Disable it again with\n--no-tftp-no-options.\n\nExample:\ncurl --tftp-no-options tftp://192.168.0.1/\n\nSee also --tftp-blksize.\n", "long": "--tftp-no-options" }, { "name": "-z, --time-cond