I use the easy interface and prepare my request using several
curl_easy_setopt calls, the first of them with the CURLOPT_ERRORBUFFER
parameter and a pointer to a buffer with sufficient space. Other calls
follow (CURLOPT_VERBOSE, CURLOPT_TIMEOUT, CURLOPT_URL, CURLOPT_USERPWD,
CURLOPT_PROXY, CURLOPT_PROXYUSERPWD, CURLOPT_SSLVERSION,
CURLOPT_SSL_VERIFYHOST, CURLOPT_SSL_VERIFYPEER, CURLOPT_CAINFO,
CURLOPT_POSTFIELDS, CURLOPT_WRITEFUNCTION, and CURLOPT_DEBUGFUNCTION)
before I call curl_easy_perform.
In case of an error code (result != CURLE_OK), I did find an error
description in the buffer I passed with the CURLOPT_ERRORBUFFER with
previous versions (7.12.0 and earlier) of cURL. In the new version, this
is not always the case. If a try a connection to an invalid host name, I
get a very precise description, but if I try to connect to a host/port
where no server ist running, the buffer is just empty in the new version.
I see the same behaviour on linux and windows machines, and after going
back to 7.12.0, the problem has gone.
This is all I know about it,
>>Did anyone else see this behaviour? I am using libcurl with openssl-0.9.7d on
>>linux (Redhat and Suse) and windows (2000 and XP) to access secure web
>>servers (SSL). Is this a bug or a feature?
>It is a bug. Can you please tell us with more details how you get an error
>with no error message?
>>Is there any workaround exept from going back to 7.12.0?
>Use curl_easy_strerror() perhaps?
Received on 2004-09-19