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: David Hu via curl-users <curl-users_at_lists.haxx.se>
Date: Sun, 10 Oct 2021 12:14:19 +0000
Thank you for the reply Daniel.
I am sorry I did not explain thoroughly about how to resolve Handshake domains.
But good news for you!
They (Handshake project) provides a public DNS resolver and supports DoH as you mentioned. It even mentioned the curl DoH command on their docs! Thank you very much Daniel and the many developer to make that happen.
"You can use curl's DoH flag to query Handshake endpoints in shell scripts easily:
curl --doh-url https://query.hdns.io/dns-query http://welcome.rb
"
Sorry for bothering you because I didn't realise that part of their docs. I will certainly read them next time.
Thanks again.
-------- Original Message --------
On Oct. 10, 2021, 01:38, Daniel Stenberg wrote:
> 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
Date: Sun, 10 Oct 2021 12:14:19 +0000
Thank you for the reply Daniel.
I am sorry I did not explain thoroughly about how to resolve Handshake domains.
But good news for you!
They (Handshake project) provides a public DNS resolver and supports DoH as you mentioned. It even mentioned the curl DoH command on their docs! Thank you very much Daniel and the many developer to make that happen.
"You can use curl's DoH flag to query Handshake endpoints in shell scripts easily:
curl --doh-url https://query.hdns.io/dns-query http://welcome.rb
"
Sorry for bothering you because I didn't realise that part of their docs. I will certainly read them next time.
Thanks again.
-------- Original Message --------
On Oct. 10, 2021, 01:38, Daniel Stenberg wrote:
> 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