CURL 7.65.3 released: tool to transfer data from or to a server

curl is a tool to transfer data from or to a server, using one of the supported protocols (HTTP, HTTPS, FTP, FTPS, SCP, SFTP, TFTP, DICT, TELNET, LDAP or FILE). The command is designed to work without user interaction.
curl offers proxy support, user authentication, FTP uploading, HTTP posting, SSL connections, cookies, file transfer resume, Metalink, and many other features.

CURL 7.65.3 released.

Changelog

Bugfixes:

• CIPHERS.md: Explain Schannel error SEC_E_ALGORITHM_MISMATCH
• CMake: Convert errant elseif() to else()
• CMake: Fix finding Brotli on case-sensitive file systems
• CURLMOPT_SOCKETFUNCTION.3: clarified
• CURLMOPT_SOCKETFUNCTION.3: fix typo
• CURLOPT_CAINFO.3: polished wording
• CURLOPT_HEADEROPT.3: Fix example
• CURLOPT_RANGE.3: Caution against using it for HTTP PUT
• CURLOPT_SEEKDATA.3: fix variable name
• DEPRECATE: fixup versions and spelling
• bindlocal: detect and avoid IP version mismatches in bind()
• build: fix Codacy warnings
• buildconf.bat: fix header filename
• c-ares: honor port numbers in CURLOPT_DNS_SERVERS
• config-os400: add getpeername and getsockname defines
• configure: –disable-progress-meter
• configure: fix –disable-code-coverage
• configure: fix typo ‘–disable-http-uath’
• configure: more –disable switches to toggle off individual features
• configure: remove CURL_DISABLE_TLS_SRP
• conn_maxage: move the check to prune_dead_connections()
• curl: skip CURLOPT_PROXY_CAPATH for disabled-proxy builds
• curl_multi_wait.3: escape backslash in example
• docs: Explain behavior change in –tlsv1. options since 7.54

More…

Download

How to use curl

Basic GET

GET a single resource via its URI

The default operation is a GET:

curl http://api.example.com:8080/statuses/1234

GET multiple resources where IDs are in a range

Use square brackets with a dashed range:

curl http://api.example.com:8080/items/[1230-1234]

GET multiple resources where IDs aren’t in a range

Use curly braces with comma-delimited strings:

curl http://api.example.com:8080/products/{abc,def,ghi}/status

Using HTTP Headers

Accept only the application/json content-type

Use the header option: -H or –header

curl -H 'Accept: application/json' http://api.example.com:8080/items/1234

Add multiple headers

Use multiple -H options:

curl -H ‘Accept: application/json’ -H ‘Accept-Encoding: gzip’ http://api.example.com:8080/products/a1b2c3ef/status

Note: the output from this is likely to be unreadable because it’s gzipped!

More likely you’d use this with ETags:

curl -H ‘Accept: application/json’ -H ‘If-None-Match: “1cc044-172-3d9aee80″‘ http://api.example.com:8080/products/a1b2c3ef/status

Show the network and HTTP “conversation”

Use the verbose option: -v or –verbose

curl -v -H http://api.example.com

POST and PUT

POST data to a URI

To send data to the server, you use either POST or PUT, depending on what the API requires. To do a POST, you simply use the -d (–data)  with some content:

curl -d "name=Ted" http://api.example.com:8080/customers

Note that this uses application/x-www-form-urlencoded as the Content-Type, i.e.,as if it was submitted by an HTML Form. You can use multiple -d options, which will be combined, e.g., these two commands produce the same content:

curl -d “first=Ted” -d “last=Young” http://api.example.com:8080/customers
curl -d “first=Ted&last=Young” http://api.example.com:8080/customers

If you want to send JSON, you’ll need to specify the Content-Type explicitly using the -H (header) option:

curl -d '{"name": "Ted"}' -H 'Content-Type: application/json' http://api.example.com:8080/items

PUT data to a URI

If you need to use the PUT method, you’ll need to override the method with the -X (–request) option:

curl -X PUT -d ‘{“name”: “Ted”}’ -H ‘Content-Type: application/json’ http://api.example.com:8080/items/1234