Struggling to understand the socket timeout

[hardysabs2]

We have a 1000ms timeout on socket and then these...
send: 10000,
response: 10000

I am struggling to properly understand what the socket step means.
"...socket starts when the socket is connected. See [request.setTimeout]..."

We are successfully sending the request to the server and the server is definitely actioning the request, though we are NOT receiving the server's response, however the timeout is not a response timeout it is a socket timeout.
I don't fully understand when the socket timeout ends and what that means and if the issue is likely to be client side (something our OS layer is not doing) or server side (something the server is not doing even though it receives and actions the request and we are not getting a response timeout per se).

Many thanks

[sindresorhus]

The socket timeout is triggered when there's no activity (no data being sent or recieved) on the connection for the specified duration. With your setup, the socket timeout is 1000ms, which is quite aggressive.

Here's what's likely happening:

1. Your request is sent successfully (within the send timeout of 10000ms)
2. The server receives and processes the request
3. However, if the server takes longer than 1000ms to start sending the response back, the socket timeout kicks in and kills the connection

Your socket timeout (1000ms) is much shorter than your response timeout (10000ms). This means even though you're allowing 10 seconds for the response, the connection will die after just 1 second of inactivity.

To fix this, you should increase the socket timeout to be at least equal to your response timeout, or remove it entirely if you don't need it:

{
	timeout: {
		send: 10000,
		response: 10000
		// Remove socket timeout or set it higher
	}
}

The issue is almost certainly the socket timeout being too short for your server's response time.