php的curl函數有多個參數:
CURLOPT_TIMEOUT_MS 設置cURL允許執行的最長毫秒數。 在cURL 7.16.2中被加入。從PHP 5.2.3起可使用。 所以使用的時候請先查看libcurl版本 curl --version
但是這個函數有個bug,如果時間小於1000毫秒也就是1秒的話,會立馬報錯,查看下面說明
If you want cURL to timeout in less than one second, you can use CURLOPT_TIMEOUT_MS, although there is a bug/"feature" on "Unix-like systems" that causes libcurl to timeout immediately if the value is < 1000 ms with the error "cURL Error (28): Timeout was reached". The explanation for this behavior is:
"If libcurl is built to use the standard system name resolver, that portion of the transfer will still use full-second resolution for timeouts with a minimum timeout allowed of one second."
What this means to PHP developers is "You can use this function without testing it first, because you can't tell if libcurl is using the standard system name resolver (but you can be pretty sure it is)"
The problem is that on (Li|U)nix, when libcurl uses the standard name resolver, a SIGALRM is raised during name resolution which libcurl thinks is the timeout alarm.
The solution is to disable signals using CURLOPT_NOSIGNAL. Here's an example script that requests itself causing a 10-second delay so you can test timeouts:
1 <?php 2 if (!isset($_GET['foo'])) { 3 // Client 4 $ch = curl_init('http://localhost/test/test_timeout.php?foo=bar'); 5 curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); 6 curl_setopt($ch, CURLOPT_NOSIGNAL, 1); 7 curl_setopt($ch, CURLOPT_TIMEOUT_MS, 200); 8 $data = curl_exec($ch); 9 $curl_errno = curl_errno($ch); 10 $curl_error = curl_error($ch); 11 curl_close($ch); 12 13 if ($curl_errno > 0) { 14 echo "cURL Error ($curl_errno): $curl_error\n"; 15 } else { 16 echo "Data received: $data\n"; 17 } 18 } else { 19 // Server 20 sleep(10); 21 echo "Done."; 22 } 23 ?>
對,增加 curl_setopt($ch, CURLOPT_NOSIGNAL, 1)