Stefan Eissing @icing@chaos.social
Public

8.19.0, released today, has my reimplementation of rate limits for up- and downloads. They work the same for all network protocols and HTTP versions, and per URL, even on shared connections.

Meaning you can mix different limits (including unlimited) on the same HTTP/2 connection.

(This was not a goal as such, mainly a side effect of doing things properly. „Technical Credit“ I would call it. 😌)

eissing.org/icing/posts/curl-r

curl rate limits

The curl project merged #19384, #20033 and #20228 which re-implements rate limiting of transfers in libcurl. This will be part of the upcoming 8.19.0 release at the beginning of March 2026. What is it, why did we change it and how? libcurl’s rate limiting libcurl offers the options CURLOPT_MAX_SEND_SPEED_LARGE and CURLOPT_MAX_RECV_SPEED_LARGE on transfers to set the limit in bytes per second for up- and downloads. This is available in the curl tool as command line option --limitrate <speed>. Running

eissing.org · icing's blog

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://chaos.social/users/icing/statuses/116209387895404536 on your instance and quote it. (Note that quoting is not supported in Mastodon.)