Buy commercial curl support. 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 Daniel himself.
Re: Any way to set connect-timeout per-IP, not global?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Dan Fandrich via curl-users <curl-users_at_lists.haxx.se>
Date: Fri, 11 Oct 2024 11:50:55 -0700
On Fri, Oct 11, 2024 at 06:47:09PM +0300, ValdikSS via curl-users wrote:
> Currently curl, when used with --connect-timeout option, uses it as a global timeout for the whole
> connection set, decreasing the timeout for each IP address in half every connection attempt.
>
> If several IP addresses from the top of DNS resolution are not working, the others (potentially
> working ones) just won't get enough timeout to establish the connection.
Why set a --connect-timeout shorter than what you're willing to accept? If you
don't mind if the connect takes longer because it has to check more addresses,
just set a longer connect timeout.
Dan
Date: Fri, 11 Oct 2024 11:50:55 -0700
On Fri, Oct 11, 2024 at 06:47:09PM +0300, ValdikSS via curl-users wrote:
> Currently curl, when used with --connect-timeout option, uses it as a global timeout for the whole
> connection set, decreasing the timeout for each IP address in half every connection attempt.
>
> If several IP addresses from the top of DNS resolution are not working, the others (potentially
> working ones) just won't get enough timeout to establish the connection.
Why set a --connect-timeout shorter than what you're willing to accept? If you
don't mind if the connect takes longer because it has to check more addresses,
just set a longer connect timeout.
Dan
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2024-10-11