Symfony version(s) affected

5.4.0

Description

We have set PHP's configuration directive default_socket_timeout to -1 (meaning infinite timeout), and noticed that all requests created with symfony/http-client failed with a "Idle timeout reached" exception.

This looked like #44198, but the issue persisted beyond upgrading from 5.3.7 to 5.4.0.

How to reproduce

ini_set('default_socket_timeout', '-1');
$response = \Symfony\Component\HttpClient\HttpClient::create()->request('GET', 'https://symfony.com');
dd($response->getStatusCode());
// Symfony\Component\HttpClient\Exception\TimeoutException with message 'Idle timeout reached for "https://symfony.com/".'

Possible Solution

The HttpClientTrait falls back to the default_socket_timeout value from PHP:

However, the TransportResponseTrait does not seem to handle this well:

Consequently (I think), the following usleep() call is skipped:

So curl may not have a chance to actually proceed with the request, and since no time is elapsed, $elapsedTimeout and $timeoutMax are still both 0, causing the following ErrorChunk:

Additional Context

Originally posted here: meilisearch/meilisearch-php#262

 Symfony\Component\HttpClient\Exception\TimeoutException: Idle timeout reached for "http://meilisearch:7700/indexes/projects/documents?primaryKey=id".
 
 /var/www/html/vendor/symfony/http-client/Chunk/ErrorChunk.php:62
 /var/www/html/vendor/symfony/http-client/Response/CommonResponseTrait.php:150
 /var/www/html/vendor/symfony/http-client/Response/TransportResponseTrait.php:55
 /var/www/html/vendor/symfony/http-client/Psr18Client.php:100
 (...)