Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: [EXTERNAL] Re: Feature request: provide ability to set a global callback function telling libcurl if IPv6 works on the system
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Dan Fandrich via curl-library <curl-library_at_lists.haxx.se>
Date: Wed, 21 Sep 2022 13:04:30 -0700
On Wed, Sep 21, 2022 at 07:40:10PM +0000, Dmitry Karpov via curl-library wrote:
> Yes, doing things "lazily" in Daniel's PR fixes the problem for explicit CURL_IPRESOLVE_V4, which will not call Curl_ipv6works() anymore.
> But the problem is still there for the CURL_IPRESOLVE_WHATEVER, which is the default value for the CURLOPT_IPRESOLVE option.
I'm clearly missing something. If Daniel's PR fixes the issue by setting
CURL_IPRESOLVE_V4, then why not just set CURL_IPRESOLVE_V4 when needed? Why do
you feel an additional callback mechanism is still needed?
Dan
Date: Wed, 21 Sep 2022 13:04:30 -0700
On Wed, Sep 21, 2022 at 07:40:10PM +0000, Dmitry Karpov via curl-library wrote:
> Yes, doing things "lazily" in Daniel's PR fixes the problem for explicit CURL_IPRESOLVE_V4, which will not call Curl_ipv6works() anymore.
> But the problem is still there for the CURL_IPRESOLVE_WHATEVER, which is the default value for the CURLOPT_IPRESOLVE option.
I'm clearly missing something. If Daniel's PR fixes the issue by setting
CURL_IPRESOLVE_V4, then why not just set CURL_IPRESOLVE_V4 when needed? Why do
you feel an additional callback mechanism is still needed?
Dan
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2022-09-21