On 9/24/22 23:07, Daniel Stenberg wrote:
On Sat, 24 Sep 2022, Patrick Monnerat via curl-library wrote:
I just noticed curl_version_info() is not thread-safe when compiled
with multi-ssl backends because the HTTPS-proxy feature bit is
computed at run-time and may change between calls.
This i
On Fri, 23 Sep 2022, Matthew Bobowski wrote:
Thank you for your response. Please let me know if I can help in any way. I
would consider donating to restore the original behavior and get it
documented 😉
I heaer there are companies offering curl support that could help you do this
for a fair p
On Fri, 23 Sep 2022, Dmitry Karpov wrote:
But how do you suggest to address the issues with "closed code" as I
outlined in my previous post?
" - if you code integrates (or will do that future) some "3rd party"
components which might be using libcurl and dual-stack resolve modes, which
you
On Sat, 24 Sep 2022, Patrick Monnerat via curl-library wrote:
I just noticed curl_version_info() is not thread-safe when compiled with
multi-ssl backends because the HTTPS-proxy feature bit is computed at
run-time and may change between calls.
This is the case until the effective SSL backend
I just noticed curl_version_info() is not thread-safe when compiled with
multi-ssl backends because the HTTPS-proxy feature bit is computed at
run-time and may change between calls.
This is the case until the effective SSL backend is selected
(curl_global_sslset() or curl_global_init()).
On Fri, Sep 23, 2022 at 11:36:16PM +0200, Daniel Stenberg via curl-library
wrote:
> What features in C17 do you think would improve curl?
While I do not encourage the switch to C17, the only advantage that
comes to my mind would be the support of instead of
CURLSHOPT_LOCKFUNC.
--Emil
--
Unsubs
