Description:
------------
Just a little thing! If you request a URL that takes longer than the allowed time to respond (as set in client options), the response correctly sets a CURL error code of 28 (http://curl.haxx.se/libcurl/c/libcurl-errors.html; CURLE_OPERATION_TIMEDOUT), but the text of the error is "Resolving timed out after <x> milliseconds". This is misleading because it's not the resolving that is timing out, but the request.

I suppose you could argue that you can apply the term 'resolving' to the fetching of a URL, but it would be unusual as that term is usually reserved for DNS lookups.

For a DNS resolution error, the curlerror would be 6 - an example error for that is:

6: Could not resolve host: <host name>

Test script:
---------------
Test target:

<?php
sleep(5);
echo 'ok';

Test script:
<?php
$request = new http\Client\Request("GET",
	"http://localhost/slow.php"
);
$request->setOptions(["timeout" => 1]);

$client = new http\Client;
try {
	$client->enqueue($request)->send();
} catch (Exception $e) {
	$response = $client->getResponse();
	$t = $response->getTransferInfo();
	echo $t->curlcode . ': ' . $t->error;
}


Expected result:
----------------
28: Operation timed out after 1000 milliseconds

Actual result:
--------------
28: Resolving timed out after 1000 milliseconds