Patrick,
It is not as clear as that, if you have a wrong LDAP request schema,
ldap returned code is also store into msg->result, when in my opinion
this is an LDAP protocol error. In any case it allows to retrieve an
classify low level errors as: invalid-credential, invalid-request, ...
which is what I was looking for.
Have a nice Sunday.
Fulup
On 02/05/2021 00:44, Patrick Monnerat via curl-library wrote:
On 5/1/21 10:15 PM, Fulup Ar Foll wrote:
@patrick: retrieving connection code with LDAP works in both
synchronous and asynchronous mode and not only in HTTP,TFTP,...
There are two things:
- the curl result code of type CURLcode: this one is always available
as this is the value returned by most functions in the API. It is
generated by curl and never transmitted across a connection.
- The protocol returned code: this code is protocol-dependent and sent
by the server within a response. You can get it with
curl_easy_getinfo(handle, CURLINFO_RESPONSE_CODE, &code). It has no
direct relationship with the curl result code.
Your initial question seemed to be about the second, that's why I
pointed you on its unavailablity for the LDAP protocol.
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
