cURL 7.84 Release Notes: New Features, Deprecations, and Bug Fixes
cURL 7.84 introduces a new –rate option to limit transfer frequency, deprecates –random-file and –egd-file, adds thread‑safety indicators, expands CA path info, supports SSH host‑key callbacks, enables Unix‑socket SOCKS proxy usage, and includes various bug fixes such as improved CMake support and .netrc handling.
cURL is a software project that provides the libcurl library and the curl command‑line tool for data transfer using various network protocols. Version 7.84 has been officially released.
Changes
-rate – a new command‑line option that limits the number of transfers per time period.
Deprecated -random-file and -egd-file ; they no longer have any effect.
curl_global_init() is now thread‑safe on most platforms.
curl_version_info now includes CURL_VERSION_THREADSAFE , allowing applications to check thread‑safety of the libcurl build.
CURLINFO_CAPATH / CURLINFO_CAINFO – expose the default CA path and file, which are usually set at build time.
CURLOPT_SSH_HOSTKEYFUNCTION – for builds with libssh2, a callback can now be set for host‑key verification.
Deprecated CURLOPT_RANDOM_FILE and CURLOPT_EGDSOCKET ; they are unused.
Unix‑socket to SOCKS proxy – libcurl can now use a Unix domain socket to connect to a SOCKS proxy instead of TCP.
Bug Fixes
Improved CMake support for libpsl and libidn2.
Repository now complies with the REUSE standard.
Headers API is no longer experimental.
Support for quoted strings in .netrc files.
Optimized case‑insensitive string comparisons.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Laravel Tech Community
Specializing in Laravel development, we continuously publish fresh content and grow alongside the elegant, stable Laravel framework.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.