Non-configurable connection timeout (60s)

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().

Start by locating Connect() and the current timeout unit test that connects to 1.1.1.2:80. Check how the 60-second timeout is applied and how a caller could configure it through Connect(). Done means the test exercises a real timeout without relying on an internet response and callers can use a configured connection timeout.

Written by the indexing model from the issue text.