On 2013-04-08 01:58, Dan Fandrich wrote:
> I'm not so sure defaulting to this is the desired behaviour. After all, the
> default behaviour for the last 10 years has been the opposite, and I don't
> recall anyone complaining until now. Changing the default would also break
> backward compatibility in a big way. For example, what happens on all those
> systems running a local caching nameserver on 127.0.0.1?

I couldn't think of any good reason why you would want to bind curl
requests to one interface and yet let DNS requests associated with the
request use the routing table per system default but the local caching
nameserver on 127.0.0.1 is a convincing example. Thanks for that.

So I agree that Ben's patches as they stand do the right thing:
introduce a new option for binding c-ares, with no backward
compatibility concerns.

-kv
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2013-04-08