HttpClient ConnectTimeout is not respected

[jarruda]

A request configured with a connect timeout of 1000ms takes at least 21 seconds to return.

RetryStrategy was set to nullptr.

[INFO] 2016-04-08 13:14:47 WinHttpSyncHttpClient [15408] Creating http client with user agent aws-sdk-cpp/0.9.6-56-g3fe46f0 Windows/6.1.7601-Service Pack 1 AMD64 with max connections 25 request timeout 3000,and connect timeout 1000
[DEBUG] 2016-04-08 13:14:47 WinHttpSyncHttpClient [15408] API handle 0000000002D2FE90.
[INFO] 2016-04-08 13:14:47 ConnectionPoolMgr [15408] Creating connection pool mgr with handle 0000000002D2FE90, and max connections per host 25, request timeout 3000 ms, and connect timeout in 1000 ms.
[TRACE] 2016-04-08 13:14:47 WinHttpSyncHttpClient [15408] Making GET request to uri xxxx
[INFO] 2016-04-08 13:14:47 WinHttpConnectionPoolMgr [15408] Attempting to aquire connection for xxxx
[DEBUG] 2016-04-08 13:14:47 WinHttpConnectionPoolMgr [15408] Pool doesn't exist for endpoint, creating...
[DEBUG] 2016-04-08 13:14:47 WinHttpConnectionPoolMgr [15408] Pool has no available existing connections for endpoint, attempting to grow pool.
[DEBUG] 2016-04-08 13:14:47 WinHttpConnectionPoolMgr [15408] Returning connection handle 0000000004C64210.
[DEBUG] 2016-04-08 13:14:47 WinHttpSyncHttpClient [15408] Acquired connection 0000000004C64210
[DEBUG] 2016-04-08 13:14:47 WinHttpSyncHttpClient [15408] AllocateWindowsHttpRequest returned handle 0000000004C64360
[DEBUG] 2016-04-08 13:14:47 WinHttpSyncHttpClient [15408] with headers:
[DEBUG] 2016-04-08 13:14:47 WinHttpSyncHttpClient [15408] host: xxxx
[WARN] 2016-04-08 13:15:08 WinHttpSyncHttpClient [15408] Send request failed: The operation timed out

[JonathanHenson]

Apparently Windows just does whatever it wants. I did however, change the setting to use WinHttpSetTimeouts and did so on the root handle. The problem I have now is that I can't get it to take longer than one second to timeout. However, this is probably because it was recieving either a dns error, or a socket reject (it's hard to get a good test case put together). I'll push an update tonight. Give it a try and let me know how it goes.

[jarruda]

My test case was with a non-existent private network address in 192.168.0.0/16. I'll try out the change as soon as I see the commit. Thanks!

[JonathanHenson]

I pushed the change out, can you have a look?

[jarruda]

That did the trick! Confirmed setting a 5s timeout worked as well:

[INFO] 2016-04-12 17:52:30 WinHttpSyncHttpClient [11292] Creating http client with user agent aws-sdk-cpp/0.10.5 Windows/6.1.7601-Service Pack 1 AMD64 with max connections 25 request timeout 3000,and connect timeout 5000
[DEBUG] 2016-04-12 17:52:30 WinHttpSyncHttpClient [11292] API handle 000000000036B1A0.
[INFO] 2016-04-12 17:52:30 ConnectionPoolMgr [11292] Creating connection pool mgr with handle 000000000036B1A0, and max connections per host 25, request timeout 3000 ms, and connect timeout in 5000 ms.
[TRACE] 2016-04-12 17:52:30 WinHttpSyncHttpClient [11292] Making GET request to uri http://192.168.44.44
[INFO] 2016-04-12 17:52:30 WinHttpConnectionPoolMgr [11292] Attempting to aquire connection for 192.168.44.44:80
[DEBUG] 2016-04-12 17:52:30 WinHttpConnectionPoolMgr [11292] Pool doesn't exist for endpoint, creating...
[DEBUG] 2016-04-12 17:52:30 WinHttpConnectionPoolMgr [11292] Pool has no available existing connections for endpoint, attempting to grow pool.
[DEBUG] 2016-04-12 17:52:30 WinHttpConnectionPoolMgr [11292] Returning connection handle 0000000000384160.
[DEBUG] 2016-04-12 17:52:30 WinHttpSyncHttpClient [11292] Acquired connection 0000000000384160
[DEBUG] 2016-04-12 17:52:30 WinHttpSyncHttpClient [11292] AllocateWindowsHttpRequest returned handle 0000000000384570
[DEBUG] 2016-04-12 17:52:30 WinHttpSyncHttpClient [11292] with headers:
[DEBUG] 2016-04-12 17:52:30 WinHttpSyncHttpClient [11292] host: 192.168.44.44

[WARN] 2016-04-12 17:52:35 WinHttpSyncHttpClient [11292] Send request failed: The operation timed out

[JonathanHenson]

Nice. Feel free to close

Sent from my iPhone

On Apr 12, 2016, at 5:54 PM, Justin Arruda notifications@github.com wrote:

That did the trick! Confirmed setting a 5s timeout worked as well:

[INFO] 2016-04-12 17:52:30 WinHttpSyncHttpClient [11292] Creating http client with user agent aws-sdk-cpp/0.10.5 Windows/6.1.7601-Service Pack 1 AMD64 with max connections 25 request timeout 3000,and connect timeout 5000
[DEBUG] 2016-04-12 17:52:30 WinHttpSyncHttpClient [11292] API handle 000000000036B1A0.
[INFO] 2016-04-12 17:52:30 ConnectionPoolMgr [11292] Creating connection pool mgr with handle 000000000036B1A0, and max connections per host 25, request timeout 3000 ms, and connect timeout in 5000 ms.
[TRACE] 2016-04-12 17:52:30 WinHttpSyncHttpClient [11292] Making GET request to uri http://192.168.44.44
[INFO] 2016-04-12 17:52:30 WinHttpConnectionPoolMgr [11292] Attempting to aquire connection for 192.168.44.44:80
[DEBUG] 2016-04-12 17:52:30 WinHttpConnectionPoolMgr [11292] Pool doesn't exist for endpoint, creating...
[DEBUG] 2016-04-12 17:52:30 WinHttpConnectionPoolMgr [11292] Pool has no available existing connections for endpoint, attempting to grow pool.
[DEBUG] 2016-04-12 17:52:30 WinHttpConnectionPoolMgr [11292] Returning connection handle 0000000000384160.
[DEBUG] 2016-04-12 17:52:30 WinHttpSyncHttpClient [11292] Acquired connection 0000000000384160
[DEBUG] 2016-04-12 17:52:30 WinHttpSyncHttpClient [11292] AllocateWindowsHttpRequest returned handle 0000000000384570
[DEBUG] 2016-04-12 17:52:30 WinHttpSyncHttpClient [11292] with headers:
[DEBUG] 2016-04-12 17:52:30 WinHttpSyncHttpClient [11292] host: 192.168.44.44

[WARN] 2016-04-12 17:52:35 WinHttpSyncHttpClient [11292] Send request failed: The operation timed out
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub