TimeoutMiddleware stops working when enabling useSocketConnectionTimeout about mappersmith HOT 2 OPEN

I haven't seen this myself, but my guess is that it could be due to this code in HTTP gateway:

    if (timeout) {
      if (!httpOptions.useSocketConnectionTimeout) {
        httpRequest.setTimeout(timeout)
      }

      httpRequest.on('timeout', () => {
        this.canceled = true
        httpRequest.abort()
        const error = createTimeoutError(`Timeout (${timeout}ms)`)
        this.dispatchClientError(error.message, error)
      })
    }

If useSocketConnectionTimeout is true then the manual setTimeout will not happen. Then it is up to node implementation to emit a timeout, this might vary between node version you are using.

Please try to debug this by logging in this code and see if you can see timeout being triggered with useSocketConnectionTimeout both as true and false. You can also experiment with different node versions to see which one works, I think this can be different in 10, 12, 14, 16 etc.

from mappersmith.

I cannot reproduce it locally so yes, I see timeouts being triggered when using locally. In production environments, where I am tunneling connections through a proxy I don't see timeouts being triggered.
Also, according to the node documentation, the only difference between setting timeout via the timeout property and the setTimeout function is that the former sets it before the socket connection is even established, while the latter waits for the socket to be connected.
https://nodejs.org/api/http.html#httprequesturl-options-callback

from mappersmith.