curl / Mailing Lists / curl-library / Single Mail
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

From: Dan Fandrich via curl-library <curl-library_at_lists.haxx.se>
Date: Wed, 21 Sep 2022 18:22:50 -0700

On Wed, Sep 21, 2022 at 06:21:08PM -0700, Dan Fandrich wrote:
> On Thu, Sep 22, 2022 at 12:24:57AM +0000, Dmitry Karpov via curl-library wrote:
> > > If Curl_ipv6works() were not called in the CURL_IPRESOLVE_V6 case, would
> > > that solve the issues that are remaining?
> >
> > Your question was:
> > "So, if libcurl eliminated that call in the CURL_IPRESOLVE_V4 case, would it fix your problem?"
>
> That was my previous question. The question above refers to CURL_IPRESOLVE_V6.
>
> > YES, adding a callback doesn't fix anything on its own. But it allows curl applications to work around problems/regressions caused by default Curl_ipv6works() behavior.
>
> I'm betting that this problem can be fixed without adding a new callback,
> especially one that goes against the way libcurl works, namely that callbacks
> are used to change behaviour during a transfer.

You also didn't answer this question:

> Since you're calling it a regression, then where did that regression occur? Was
> it in libcurl or in the kernel? Maybe this problem needs to be solved
> elsewhere.
-- 
Unsubscribe: https://lists.haxx.se/listinfo/curl-library
Etiquette:   https://curl.se/mail/etiquette.html
Received on 2022-09-22