I assume you mean two things when you say “handle”:
- If the script connects to a “wrong” proxy, it will wait for a long time to establish the connection, until it times out. The script should set a lower timeout, so users don't wait forever.
- If an error occures during accessing the external ressource, don't die or show ugly messages. Instead, pretend everything's cool.
As for 1) The timeout of a remote connection is defined in PHP's default_socket_timeout
setting and is by default 60 seconds. You can/should set a much lower timeout for your own calls:
$opts = array(
'http'=>array(
'timeout'=> 2, // timeout of 2 seconds
'proxy' => 'tcp://100.100.100.100:80' //a wrong proxy
)
);
As for 2), you would normally use a try
/catch
block. Unfortunately, file_get_contents()
is one of those old PHP functions that don't throw catchable exceptions.
You can supress a possible error message by prefixing the function call with the @
sign:
$file = @file_get_contents('http://ifconfig.me/ip', false, $context);
But then you can't handle any errors at all.
If you want to have at least some error handling, you should use cURL. Unfortunately, it also doesn't throw exceptions. However, if a cURL error occurs, you can read it with curl_errno()
/curl_error()
.
Here's your code implemented with cURL:
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, "http://ifconfig.me/ip");
curl_setopt($ch, CURLOPT_PROXY, 'tcp://100.100.100.100:80');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_TIMEOUT, 2);
curl_setopt($ch, CURLOPT_HEADER, 1);
$data = curl_exec($ch);
$error = curl_errno($ch) ? curl_error($ch) : '';
curl_close($ch);
print_r($error ? $error : $data);
This way, you can decide what you want to do in the case of an error.