Daniel,
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).
May be in a futture version 😇.
Have a nice weekend.
Fulup
On 01/05/2021 00:47, Daniel Stenberg wrote:
On Fri, 30 Apr 2021, Fulup Ar Foll via curl-library wrote:
+ curl_multi_info_read return CURLMSG_DONE
Allow me to quote curl_multi_info_read.3:
When msg is CURLMSG_DONE, the message identifies a transfer that is
done,
and then result contains the return code for the easy handle that just
completed.
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
