CURL 7.65.1 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.1 released.

Changelog

Bugfixes:

• CURLOPT_LOW_SPEED_* repaired
• NTLM: reset proxy “multipass” state when CONNECT request is done
• PolarSSL: deprecate support step 1. Removed from configure
• appveyor: add Visual Studio solution build
• cmake: check for if_nametoindex()
• cmake: support CMAKE_OSX_ARCHITECTURES when detecting SIZEOF variables
• config-win32: add support for if_nametoindex and getsockname
• conncache: Remove the DEBUGASSERT on length check
• conncache: make “bundles” per host name when doing proxy tunnels
• curl-win32.h: Enable Unix Domain Sockets based on the Windows SDK version
• curl_share_setopt.3: improve wording
• dump-header.d: spell out that no headers == empty file
• example/http2-download: fix format specifier
• examples: cleanups and compiler warning fixes
• http2: Stop drain from being permanently set
• http: don’t parse body-related headers in bodyless responses
• md4: build correctly with openssl without MD4
• md4: include the mbedtls config.h to get the MD4 info
• multi: track users of a socket better
• nss: allow to specify TLS 1.3 ciphers if supported by NSS
• parse_proxy: make sure portptr is initialized
• parse_proxy: use the IPv6 zone id if given
• sectransp: handle errSSLPeerAuthCompleted from SSLRead()
• singlesocket: use separate variable for inner loop
• ssl: Update outdated “openssl-only” comments for supported backends
• tests: add HAProxy keywords
• tests: add support to test against OpenSSH for Windows
• tests: make test 1420 and 1406 work with rtsp-disabled libcurl
• tls13-docs: mention it is only for OpenSSL >= 1.1.1
• tool_parse_cfg: Avoid 2 fopen() for WIN32
• tool_setopt: for builds with disabled-proxy, skip all proxy setopts()
• url: Load if_nametoindex() dynamically from iphlpapi.dll on Windows
• url: fix bad feature-disable #ifdef
• url: use correct port in ConnectionExists()
• winbuild: Use two space indentation

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