Re: Disable DNS over HTTPS (DoH) on command line
Date: Wed, 20 Nov 2019 23:47:55 +0100 (CET)
On Wed, 20 Nov 2019, dumblob via curl-users wrote:
> My main concern is, that if at some point curl will be released and will
> bundle even just one default/recommended/you_name_it DoH server, then I'm
> totally screwed.
Not only you I would guess. It would be a breaking behavior that for sure
would break things for a huge portion of users. I can't for the life of me
think of a reason why we would ever do that.
> If passing --doh-url "" will have precedence over any such behavior, then
> it's the solution I'm looking for. If not, how do I prevent it?
You're basically asking for a way to deal with the case if we would go totally
insane and change curl in a way we've promised never to do and which we work
HARD every fricking day to stay true to?
I don't think we can offer even a theoretical solution for that "risk".
Because it would be an earth shattering moment in this project and if we would
break such a fundamental rule then I would guess that all the other rules
would also be up for grabs.
I can very well imagine that a future version curl will automatically use DoH
on some systems where it can detect that it works or where the OS and its
resolver provides that for applications. But then I also imagine that admins
who really don't want that used on their machines and networks would then not
make that happen. Or set it up to work according to their own desires and
requests. That's also a theoretical future that I can't really speak much of
now because we have no idea how that will play out - *if* it even ever will
-- / daniel.haxx.se | Get the best commercial curl support there is - from me | Private help, bug fixes, support, ports, new features | https://www.wolfssl.com/contact/ ----------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2019-11-20