On Thu, 9 Apr 2009, Sandeep Kale wrote:
I have used mutex callbacks, however the issue of server going into a hang
state still persisted. Below is a code snippet where I suspect the issue is
present.
And is this now using a recent libcurl version?
//! Return curl error if any.
How exactly did you simulate this?
We have set the url and the port number to a non-existing server and
non-existing port. This generated the trace as below,
* About to connect() to 192.172.47.64 port 7878 (#0)
* Trying 3.142.47.64... * Connection refused
* couldn't connect to host
* Closing
Hi,
We are using the libcurl version as below,
-- libcurl version
curl 7.18.1 (sparc-sun-solaris2.10) libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.1.3
Protocols: tftp ftp telnet dict ldap http file https ftps
Features: IPv6 Largefile NTLM SSL
On Mon, 6 Apr 2009, Sandeep Kale wrote:
We have developed a server which has libcurl at its heart. It processes all
kind of http / soap requests. This server goes into a hang state once it
receives a curl return code as CURLE_COULDNT_CONNECT, the server process
doesn't crash neither it
On Mon, Apr 06, 2009 at 07:32:53PM +0530, Sandeep Kale wrote:
We are using the libcurl version as below,
-- libcurl version
curl 7.18.1 (sparc-sun-solaris2.10) libcurl/7.18.2 OpenSSL/0.9.8g zlib/1.1.3
Can you reproduce this with the most recent
