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: libcurl LDAP in asyncmod
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_cool.haxx.se>
Date: Sat, 1 May 2021 18:15:10 +0200 (CEST)
On Sat, 1 May 2021, Fulup Ar Foll wrote:
> As the error status exist in synchronous mode, it is obvious that you handle
> it somewhere. I would have hope to get it from curl_easy_getinfo with
> something like:
>
> curl_easy_getinfo(httpRqt->easy, CURLINFO_xxxxx_xxxxx, &code);
>
> Unfortunately from what I understand the code "invalid_credential" is not
> store into curl_easy_getinfo. With current behavior, I got CURLMSG_DONE
> without any data, this allow me to understand something went wrong, but I
> cannot make the difference in between a wrong LDAP search and invalid
> credentials (in both case socket connection is established and no data
> return).
You told us how curl_easy_perform() would return an error code for this
situation. I explained how you get the exact same error code when you instead
use the multi interface.
That has nothing to do with curl_easy_getinfo().
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2021-05-01
Date: Sat, 1 May 2021 18:15:10 +0200 (CEST)
On Sat, 1 May 2021, Fulup Ar Foll wrote:
> As the error status exist in synchronous mode, it is obvious that you handle
> it somewhere. I would have hope to get it from curl_easy_getinfo with
> something like:
>
> curl_easy_getinfo(httpRqt->easy, CURLINFO_xxxxx_xxxxx, &code);
>
> Unfortunately from what I understand the code "invalid_credential" is not
> store into curl_easy_getinfo. With current behavior, I got CURLMSG_DONE
> without any data, this allow me to understand something went wrong, but I
> cannot make the difference in between a wrong LDAP search and invalid
> credentials (in both case socket connection is established and no data
> return).
You told us how curl_easy_perform() would return an error code for this
situation. I explained how you get the exact same error code when you instead
use the multi interface.
That has nothing to do with curl_easy_getinfo().
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://www.wolfssl.com/contact/
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2021-05-01