There's a list here: https://curl.se/docs/libs.html

Edit: Summary:

  SSL/TLS: OpenSSL, mbed, GnuTLS, NSS TLS, wolfSSL
  decompression: zlib
  ldap: OpenLDAP LDAP support
  kerberos/spnego: heimdal, MIT Kerberos
  http2: nghttp2
  async dns: c-ares
  idn domains: libidn
  scp/sftp: libssh2

Note this isn't complete, it lists only 5 out of the 14 TLS libraries that cURL can be built for: https://daniel.haxx.se/blog/wp-content/uploads/2021/02/Scree... (source: https://daniel.haxx.se/blog/2021/02/09/curl-supports-rustls/ )

Of course, it does include the two that cover 95+% of uses in OpenSSL and GnuTLS.

At least libproxy itself doesn't have any dependencies

https://libproxy.github.io/libproxy/ says "no external dependencies within libproxy core (libproxy plugins may have dependencies)"

Interesting choice to have a set of FAQ in your docs without also providing answers to them. I suppose the term FAQ does sort of imply it is just the "questions".

haha, good point

The core doesn't have any dependencies, but it can support a bunch of different modules. Most notably is JavaScript to execute PAC files (WebKit, mozjs, etc.)

For macOS it calls "JSEvaluateScript(this->jsctx, str, NULL, NULL, 1, NULL)".

Obviously this kind of stuff is useful for some people, but yeah ... I'd be hesitant too; not because whether libproxy might be good or bad, but rather the nature of what it does (execute code).

Sooo does it implement http ? Coz having lib to search for proxy (it supports few http auto config methods) with its own implementation of http to use in http library would be kinda silly

open-source curl, or corporate curl?

Apple and MSFT build their own replacements for TLS and use those, others? part of a trend to replace and extend GPL software, and control critical network functions on their platforms ?

but then, others seem to want to make TLS, too ?

    [ Windows native SSL/TLS, schannel ]
    [ Apple OS native SSL/TLS, secure-transport ]
    [ GNU TLS ]
    [ mbedtls, wolfssl, mesalink, bearssl, rust-tls, nss]