It turns out c-ares returns an error when asked to resolve a host name with
ares_getaddrinfo using port number 0.
Reported as a c-ares bug here: c-ares/c-ares#517
The work-around is to simply use port 80 instead, as the number typically does
not make a difference and a non-zero number works for c-ares.
Reported-by: Matt Jolly
I did this
I expected the following
Test 1083 should pass. When configured without ares the test passes successfully.
curl 7.88.1 (x86_64-pc-linux-gnu) libcurl/7.88.1 OpenSSL/3.0.8 zlib/1.2.13 c-ares/1.19.0 nghttp2/1.52.0
Linux obsidian 6.2.0-gentoo #3 SMP PREEMPT_DYNAMIC Fri Feb 24 23:33:12 AEDT 2023 x86_64 AMD Ryzen 7 3700X 8-Core Processor AuthenticAMD GNU/Linux
The text was updated successfully, but these errors were encountered: