Problem
The CURL client currently passes NULL to CURLOPT_ACCEPT_ENCODING, which means it does not advertise any supported compression encodings in the Accept-Encoding request header. As a result, servers never send compressed responses, leading to unnecessarily high bandwidth usage.
Proposed Solution
Change CURLOPT_ACCEPT_ENCODING from NULL to "" (empty string). Per the CURL documentation, passing an empty string causes CURL to:
- Advertise all compression encodings it supports (e.g. gzip, deflate, br, zstd) via the
Accept-Encoding header
- Automatically decompress responses that use those encodings
This is a one-line change that can significantly reduce bandwidth for HTTP transfers.
Problem
The CURL client currently passes
NULLtoCURLOPT_ACCEPT_ENCODING, which means it does not advertise any supported compression encodings in theAccept-Encodingrequest header. As a result, servers never send compressed responses, leading to unnecessarily high bandwidth usage.Proposed Solution
Change
CURLOPT_ACCEPT_ENCODINGfromNULLto""(empty string). Per the CURL documentation, passing an empty string causes CURL to:Accept-EncodingheaderThis is a one-line change that can significantly reduce bandwidth for HTTP transfers.