Re:Curl doesn't add libproxy due to its quality issues
by Macha on Sunday October 23, 2022 @09:01AM
(#33306644)
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.
Re:Curl doesn't add libproxy due to its quality issues
by ape4 on Sunday October 23, 2022 @08:53AM
(#33306576)
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)"
Re:Curl doesn't add libproxy due to its quality issues
by markphip on Sunday October 23, 2022 @08:59AM
(#33306621)
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".
Re:Curl doesn't add libproxy due to its quality issues
by ape4 on Sunday October 23, 2022 @10:09AM
(#33307139)
haha, good point
Re:Curl doesn't add libproxy due to its quality issues
by Beltalowda on Sunday October 23, 2022 @10:24AM
(#33307262)
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).
Edit: Summary: