Buy commercial curl support from WolfSSL. 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
himself.
Re: Maybe consider support Handshake names (N.B. NOT TLS/SSL handshake, please read the content from details)
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-users <curl-users_at_lists.haxx.se>
Date: Sun, 10 Oct 2021 10:38:16 +0200 (CEST)
On Sun, 10 Oct 2021, David Hu via curl-users wrote:
> Unfortunately curl doesn't currently support this type of name resolution
> even if the system configured DNS supports it It will only return the
> following for example https://testdomain/
I don't know what made you think this. To my knowledge, curl shouldn't need
any changes at all in order to support other name domains or DNS roots.
curl supports normal DNS and file based name lookups in all builds. If you
build it with "stock" name resolver support it'll support whatever
getaddrinfo() supports.
> curl: (6) Could not resolve host: testdomain
That's because your name resolver doesn't recognize it. Compare to my system
on which I have a "fake.curl" host (which has a local representation of the
curl web site):
$ curl fake.curl
[lots of contents]
curl itself doesn't know how it gets the IP address for this name, it just
asks the name resolver for it and it gets a set of addresses back.
Alternatively you could point curl to use your DoH server for name resolution
and your DoH server could support that handshake system.
> If you are interested you can maybe consider it as a feature in future cURL
> development.
Feel free to elaborate on what's missing because I don't understand!
Date: Sun, 10 Oct 2021 10:38:16 +0200 (CEST)
On Sun, 10 Oct 2021, David Hu via curl-users wrote:
> Unfortunately curl doesn't currently support this type of name resolution
> even if the system configured DNS supports it It will only return the
> following for example https://testdomain/
I don't know what made you think this. To my knowledge, curl shouldn't need
any changes at all in order to support other name domains or DNS roots.
curl supports normal DNS and file based name lookups in all builds. If you
build it with "stock" name resolver support it'll support whatever
getaddrinfo() supports.
> curl: (6) Could not resolve host: testdomain
That's because your name resolver doesn't recognize it. Compare to my system
on which I have a "fake.curl" host (which has a local representation of the
curl web site):
$ curl fake.curl
[lots of contents]
curl itself doesn't know how it gets the IP address for this name, it just
asks the name resolver for it and it gets a set of addresses back.
Alternatively you could point curl to use your DoH server for name resolution
and your DoH server could support that handshake system.
> If you are interested you can maybe consider it as a feature in future cURL
> development.
Feel free to elaborate on what's missing because I don't understand!
-- / 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/listinfo/curl-users Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2021-10-10