Oh! I think I was confused by this part: " The behaviour is a little different when switching server (for instance, with the Python one, error is a timeout 28). I really don't understand what's happening and would be glad to have an explantion about what I'm missing."
So, I thought that it wasn't clear why timeouts were happening. Thanks, Dmitry Karpov -----Original Message----- From: Daniel Stenberg <dan...@haxx.se> Sent: Wednesday, March 20, 2024 3:40 PM To: Dmitry Karpov via curl-library <curl-library@lists.haxx.se> Cc: Dmitry Karpov <dkar...@roku.com> Subject: [EXTERNAL] Re: A single request in loop on macOS On Wed, 20 Mar 2024, Dmitry Karpov via curl-library wrote: > "To me, that indicates that a resource of some sort has run out, which > possibly makes curl fail to create the new socket." > > I think it is fair to expect that if libcurl fails to create a new > socket, then it will fail the transfer instantly with an error code > different from timeout, isn't it? The output he showed from his program said error code 7, that is CURLE_COULDNT_CONNECT. Not a timeout. -- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
