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: CURLOPT_DNS_SHUFFLE_ADDRESSES and CURLOPT_CONNECT_TO
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_lists.haxx.se>
Date: Fri, 25 Sep 2026 09:53:25 +0200 (CEST)
On Thu, 24 Sep 2026, Vladimir Levijev via curl-library wrote:
> We noticed this strange thing when using CURLOPT_DNS_SHUFFLE_ADDRESSES
> together with CURLOPT_CONNECT_TO curl fails with "Couldn't resolve host
> name”.
That sounds like a bug.
> Now, the reason we want to turn on “shuffling” is for the redirects. So we
> say, connect to this specific IP address, but in case of redirection, when
> resolving the hostname of the next target, use shuffling. Is it even
> possible?
I would recommend you do the redirect logic yourself (with
CURLINFO_REDIRECT_URL), as then you can easily use shuffling for the second
request only.
Date: Fri, 25 Sep 2026 09:53:25 +0200 (CEST)
On Thu, 24 Sep 2026, Vladimir Levijev via curl-library wrote:
> We noticed this strange thing when using CURLOPT_DNS_SHUFFLE_ADDRESSES
> together with CURLOPT_CONNECT_TO curl fails with "Couldn't resolve host
> name”.
That sounds like a bug.
> Now, the reason we want to turn on “shuffling” is for the redirects. So we
> say, connect to this specific IP address, but in case of redirection, when
> resolving the hostname of the next target, use shuffling. Is it even
> possible?
I would recommend you do the redirect logic yourself (with
CURLINFO_REDIRECT_URL), as then you can easily use shuffling for the second
request only.
-- / daniel.haxx.se || https://rock-solid.curl.dev
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2026-09-25