Hello Daniel,

Wednesday, January 26, 2011, 5:00:27 PM, you wrote:

> On Wed, 26 Jan 2011, 127546_at_sms13.de wrote:

>> what do you think we should do then? Try this from C or command line outside
>> of PHP?

> Yes. We need to narrow down things.

> I tried this:

> [shell 1]
> $ nc -p 9999 -l

> [shell 2]
> $ curl localhost:9999 -m3

> ... and it timed out after exactly 3000 milliseconds.

I did some more research here, first of all I cannot reproduce my problem on command line because
command line does not support milliseconds, and it seems the issue arises only when you specify
milliseconds!!!

when we changed CURL options in php into seconds the issue does not arise!! The bug is clearly in
the millisecond settings but we need milliseconds. I can see many people on google complaining abotu
this option not working correctly. I am desperate here as you see, I am willing to pay for someone
to fix this for me!!

Also I find this post of yours: http://comments.gmane.org/gmane.comp.web.curl.library/29210
where you say

"CURLOPT_CONNECTTIMEOUT does not really work for the multi interface in any
released libcurl version. We're working on making sure it works correctly
for the next release."

ps. we found similar problem with
curl_setopt($conn[$i],CURLOPT_CONNECTTIMEOUT_MS,300);

we set 500ms but the error message is Connection timed out after 1001 milliseconds

as I stated earlier I am willing to pay to get this fixed

-- 
Best regards,
 127546                            mailto:127546_at_sms13.de
_______________________________________________
http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-and-php