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: Feature request about curlinfo option returning resolver status/error code
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Dan Fandrich via curl-library <curl-library_at_lists.haxx.se>
Date: Tue, 19 Apr 2022 15:26:19 -0700
On Tue, Apr 19, 2022 at 04:14:23PM -0400, Timothe Litt via curl-library wrote:
> No. No need to invent abstract codes. Use the DNS RCODE + (if available) the
> ENS EDNS0 EDE (RFC8914).
But do those codes include errors that only a local resolver might face? Things
like access or syntax errors on /etc/resolv.conf, inability to connect to the
local resolver daemon, or out of memory? In just looking at the set of c-ares
error codes, they're defined in sections with 6 in the "server error codes"
section and 11 in the "locally-generated error codes" section.
Date: Tue, 19 Apr 2022 15:26:19 -0700
On Tue, Apr 19, 2022 at 04:14:23PM -0400, Timothe Litt via curl-library wrote:
> No. No need to invent abstract codes. Use the DNS RCODE + (if available) the
> ENS EDNS0 EDE (RFC8914).
But do those codes include errors that only a local resolver might face? Things
like access or syntax errors on /etc/resolv.conf, inability to connect to the
local resolver daemon, or out of memory? In just looking at the set of c-ares
error codes, they're defined in sections with 6 in the "server error codes"
section and 11 in the "locally-generated error codes" section.
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2022-04-20