The connection timeout is 60 seconds, if the remote end is not properly responding. The current unit test that does a tmeout test is not doing that test -- instead it is doing a test connecting to 1.1.1.2:80 (which is a web server that responds, if the machine you run tests on has internet access), so it's testing against a webserver that gives an error response instead. I'll submit a PR for a test that actually tests a timeout and exposes this 60 second timeout.
It would be ideal if timeouts could be used with Connect().
The connection timeout is 60 seconds, if the remote end is not properly responding. The current unit test that does a tmeout test is not doing that test -- instead it is doing a test connecting to 1.1.1.2:80 (which is a web server that responds, if the machine you run tests on has internet access), so it's testing against a webserver that gives an error response instead. I'll submit a PR for a test that actually tests a timeout and exposes this 60 second timeout.
It would be ideal if timeouts could be used with Connect().