On Tue, 3 Jul 2012, Marco Strohner wrote:

> For both scenarios the return value of curl_easy_perform() is
> "CURLE_COULDNT_CONNECT".

That's incorrect. libcurl doesn't return CURLE_COULDNT_CONNECT for any of
those two scenarios. CURLE_COULDNT_CONNECT means the TCP connect negotiation
failed, so there was no HTTP sent in any direction.

> Are there any other possibilities to check at which state the disconnect has
> been occured?

libcurl reports different error codes and you can also make some good guesses
depending on which callbacks that have been used or not.

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html