curl / Mailing Lists / curl-library / Single Mail
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

From: Daniel Gustafsson via curl-library <curl-library_at_lists.haxx.se>
Date: Sat, 30 Apr 2022 21:48:42 +0200

> On 30 Apr 2022, at 12:42, Daniel Stenberg via curl-library <curl-library_at_lists.haxx.se> wrote:
>
> On Mon, 25 Apr 2022, Dmitry Karpov wrote:
>
>> So, as far as documentation is concerned, I was envisioning that this feature will be documented as "opaque resolver code, which meaning depends on the used resolver backend". Because this is a debugging feature, there is no need to document more in libcurl, and the application developers can look it up in the resolver code and provide a better information/description if needed.
>
> Shouldn't that value then rather just get shown with an infof() call?

Yes, a backend agnostic error code with the backend specific information added
with infof(). This is what we do for other variable-backend subsystems and I
don't see why this would benefit from being different.

--
Daniel Gustafsson		https://vmware.com/
-- 
Unsubscribe: https://lists.haxx.se/listinfo/curl-library
Etiquette:   https://curl.haxx.se/mail/etiquette.html
Received on 2022-04-30