connection is still name resolving, cant reuse?

[bethebest0622]

I did this

curl reuse connection can save much time, when sending http get/post request repeatly.

I used it for a long time, but recently i found the messge:

* processing: http://471646160aapi.hbdm.com/linear-swap-api/v1/swap_cross_cancel?AccessKeyId=630ffb31-bgbfh5tv3f-3eb9569d-895e0&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2024-04-15T13%3A20%3A18&Signature=wNb%2BSWQtPh4VqLjtzglS9iUh2pu3BVkKjegP61ILWg8%3D
* Found bundle for host: 0x7f5c640076b0 [serially]
* Can not multiplex, even if we wanted to
* Connection #0 is still name resolving, can't reuse
* Connection #1 is still name resolving, can't reuse
* Connection #2 is still name resolving, can't reuse
* Connection #3 is still name resolving, can't reuse
* Connection #4 is still name resolving, can't reuse
* Connection #5 is still name resolving, can't reuse
* Connection #6 is still name resolving, can't reuse
* Connection #7 is still name resolving, can't reuse
* Hostname 471646160aapi.hbdm.com was found in DNS cache
*   Trying 172.31.9.166:80...
* getpeername() failed with errno 107: Transport endpoint is not connected
* Connected to 471646160aapi.hbdm.com () port 80
* getpeername() failed with errno 107: Transport endpoint is not connected
> * processing: http://471646160aapi.hbdm.com/linear-swap-api/v1/swap_cross_cancel?AccessKeyId=630ffb31-bgbfh5tv3f-3eb9569d-895e0&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2024-04-15T13%3A20%3A18&Signature=wNb%2BSWQtPh4VqLjtzglS9iUh2pu3BVkKjegP61ILWg8%3D
* Found bundle for host: 0x7f5c640076b0 [serially]
* Can not multiplex, even if we wanted to

it shows not reuse the connection even there is existed connections, could you help on this, how can i reuse connections correctly?

I expected the following

reuse the connections

curl/libcurl version

curl 8.2.1

operating system

centos stream 8

[bagder]

Thanks a lot for your report!

I've failed to reproduce this problem myself, so can I ask you to provide us with more details on how to go ahead and repeat this. Preferably with a command line or a stand-alone program we can run from our ends against a public URL to trigger the problem?

[bethebest0622]

Thanks a lot for your report!

I've failed to reproduce this problem myself, so can I ask you to provide us with more details on how to go ahead and repeat this. Preferably with a command line or a stand-alone program we can run from our ends against a public URL to trigger the problem?

Sadly, it's a private URL, i will try to reproduce it tomw with public URL, then give you the details if it's reproduceable

[bagder]

Any update? There is nothing here for us to act on unless we get a lot more information.

[bethebest0622]

I am afraid that i can't reproduce it with another public ip.

it happened only in my private host ip, it's a http url

[bagder]

If you can't provide us with a recipe then we cannot act on this at all unless you give us a lot more information about exactly what's going on and what you are doing at the moment of the problem. And of course: please first verify that the latest release also reproduces this problem before you spend a lot of time and effort on chasing it. Maybe it is already fixed.