Skip to main content


Remember #curl --libcurl, one of my all time favorite options.

(blog post from two years ago)

daniel.haxx.se/blog/2022/09/12…

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

Wooow that sound really nice. I must admit that curl and especially its API always seems hard to get into. But knowing that I only need to learn (or try on) the CLI and it can generate the code for me might tempt me next time I need to choose a network lib.

(For now Qt’s and rust’s reqwest have been very easy to use, but if next time I’m not in rust or without Qt, why not.)

in reply to Zykino

1) I saw a little typo:
> The --libcurl command line option was added to curl already back in 2007 and has been **been** part of the tool since version 7.16.1.
2) A little reminder of the command used in the top comment of the file would be awesome.
3) How do you do this? I’m so intrigued. Some logging at function start that print with its arguments?
4) If `openssl` had that, it would make using it so much simpler. They have too much public functions, and we never now if we found the top/easy level, or the final do_work function… as a newcomer.
in reply to Zykino

@Zykino 1 -fixed 2 - a good idea, yes. 3 - just about every function call made to libcurl in the tool also adds a line to the potential --libcurl output. 4 - no one ever fully understands the OpenSSL API. It is simply too large and too inconsistent.