Dan, thanks for responding.
The software is written in Eiffel, with which I would guess you are
not familiar. And you would need to read through a significant
number of classes to get the overall picture.
I have discovered the problem only occurs when using libevent2 to
drive the multi
Hello,
Yes, it's time for a final review and chance to comment on this before I
merge!
https://github.com/curl/curl/pull/5868
--
/ daniel.haxx.se
| Commercial curl support up to 24x7 is available!
| Private help, bug fixes, support, ports, new features
| https://www.wolfssl.com/contact/
On Wed, Oct 21, 2020 at 03:50:00PM +0100, MS via curl-library wrote:
> Gisle: thank you for your response.
>
>
> Let's focus on the different behaviour with IPv4:
>
> Using libcurl in an application, without firewall
> operating, attempting to connect to bbc.co.uk,
> I obtain a hang with
>
> *
Gisle: thank you for your response.
Let's focus on the different behaviour with IPv4:
Using libcurl in an application, without firewall
operating, attempting to connect to bbc.co.uk,
I obtain a hang with
* Trying 151.101.64.81:80...
the only output written.
Using curl.exe I obtain
MS wrote:
1)
Using libcurl without a proxy, the verbose options shows "Trying ip address"
and nothing else.
If restricted to IPv4 it shows only one line. If IPv6 is permitted, I get a
first response that network
is not reachable and then a second response "Trying ..." which hangs.
Some
I have a hang that I am attempting to resolve.
1)
Using libcurl without a proxy, the verbose options shows "Trying ip
address" and nothing else.
If restricted to IPv4 it shows only one line. If IPv6 is permitted, I
get a first response that network
is not reachable and then a second
On Mon, 14 Sep 2020, Daniel Stenberg via curl-library wrote:
https://github.com/curl/curl/pull/5896
My thinking is to get this merged in the *next* feature window, thus probably
in the 7.74.0 release.
The time has come. I will merge this "soon".
--
/ daniel.haxx.se
| Commercial curl
