Skip to main content


Top-5 #curl version distribution among requests done on haxproxy.org in June 2024:

curl/7.81.0 79.64%
curl/7.61.1 5.88%
curl/7.68.0 5.47%
curl/7.29.0 2.00%
curl/8.5.0 1.31%

mailarchive.ietf.org/arch/msg/…

#curl
in reply to daniel:// stenberg://

Ranked number 4: curl/7.29.0

Released on February 6 2013, approaching 11.5 years ago. We have documented >8,000 bugfixes since then...

in reply to daniel:// stenberg://

have you ever considered moving curl to using a date-based versioning scheme?
in reply to daniel:// stenberg://

True, though I've always found it difficult to know how fresh any given curl version is by number alone, and given how infrequently y'all break the API
in reply to daniel:// stenberg://

that's good to know! Most of the time I'm looking at reports with just the version, without access to the system itself. I should ask about having them include the release date with that data.
in reply to daniel:// stenberg://

I guess that might be instances of RHEL7, which technically is still supported until June 30? That should have at least the security patches backported, maybe even some bugfixes.
in reply to daniel:// stenberg://

7.29.0 is the version included in #RHEL7 (and thus #CentOS7), which is very common in enterprise systems. The binary still report 7.29.0, but the RPM has had 59 patch releases since the initial release.

RHEL 7 is EOL on Sunday this week, so numbers might start to decline soon.

in reply to Billy O'Neal

@malwareminigun yeps, I already linked my blog post in that thread. I'm pretty sure the audience on that list is aware.

The original question was however "on the web" so I think it was more about how come the browsers don't use it more than ~30%.