You think? Please make sure before you submit a bug report and set this status to "Open" if confirmed

Sorry, it was not "think", but I checked it.

-- example
-- true case
curl = curl_easy_init();
curl_easy_setopt(curl, CURLOPT_URL, "http://example.com/");
curl_easy_setopt(curl, CURLOPT_CONNECTTIMEOUT_MS, 1000);
res = curl_easy_perform(curl);

res == CURLE_OK


-- false case
curl = curl_easy_init();
curl_easy_setopt(curl, CURLOPT_URL, "http://example.com/");
curl_easy_setopt(curl, CURLOPT_CONNECTTIMEOUT_MS, 999);
res = curl_easy_perform(curl);

res != CURLE_OK

and curl_error message is "Timeout was reached"


This is the specification of cURL? if it is truth, we must confirm it and PHP documentation.

Thanks, I'll assign this to myself and will update the relevant documentation accordingly

Thanks, I'll assign this to myself and will update the relevant documentation accordingly

This bug has been fixed in SVN.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.

"If libcurl is built to use the standard system name resolver, that portion of the connect will still use full-second resolution for timeouts with a minimum timeout allowed of one second."