Laminas Http Client setTimeout versus Curl connect and read timeouts

Timeout Behavior in Laminas Http Client

Laminas\\Http\\Client::setTimeout() does not enforce distinct connection and read limits across adapters; it provides a single, unified timeout value that adapters interpret according to their own internal logic. Because there is no shared specification for "connect" vs "read" timeouts in the base client API, this method cannot be used to set separate limits portably.

Adapter-Specific Implementation

The behavior of setTimeout() varies by the active adapter:

• Curl Adapter: The value is mapped to CURLOPT_TIMEOUT, which limits the entire transfer duration (connection + data transfer).
• Socket Adapter: The value typically maps to stream_set_timeout, which primarily functions as a read timeout.

Separate Connect and Read Limits

Using setCurlOptions() on the Curl adapter is the only documented way to separate these limits. This approach couples your code to the Curl adapter and will fail or be ignored if the adapter is switched to Socket.

// Example: Separate limits using the Curl adapter
$client = new \\Laminas\\Http\\Client();
$client->setAdapter(new \\Laminas\\Http\\Client\\Adapter\\Curl());

// Set connection timeout to 2s and total request timeout to 30s
$client->getAdapter()->setCurlOptions([
    CURLOPT_CONNECTTIMEOUT => 2,
    CURLOPT_TIMEOUT        => 30,
]);

Request Cancellation

There is no supported mechanism to cancel an in-flight request via a cancellation token or interrupt signal without destroying the adapter instance or allowing the timeout to expire. Once send() is called, the execution is synchronous and blocking until the adapter returns a response or hits a timeout.

Verification Steps

To verify your timeout configuration, you can test against a non-routable IP address (e.g., 10.255.255.1):

1. Set CURLOPT_CONNECTTIMEOUT to 1 second and CURLOPT_TIMEOUT to 30 seconds.
2. Execute the request. If the request fails in approximately 1 second, the connection timeout is functioning.
3. Switch to the Socket adapter; you will observe that setCurlOptions is no longer effective, confirming the lack of portability.

Diagnostic Note: Are you running this in a CLI environment or via a web server? If the latter, max_execution_time in php.ini may trigger before the client timeout expires, masking the adapter's behavior.