Consider setting HTTP.jl's idle_timeout option

[samoconnor]

idle_timeout stops pooled connections from being reused when they've been sitting idle for too long (in which case the server has probably already dropped the other end of the connection).

It seems that there isn't a one-size-fits-all idle_timeout for AWS services. IAM seems to process requests on a connection that has been idle for up to about 50 seconds, but S3 connections seem to become unusable after about 5 seconds.

[samoconnor]

This may solve the problem: JuliaLang/MbedTLS.jl#145

[mattBrzezinski]

Closing this issue, looks like it was resolved with the fix mentioned in the comment above:

JuliaCloud/AWSS3.jl#28

[iamed2]

Did you see this comment?

Note that the idle_timeout= change to GitHub.jl is still desirable because there is a race-condition when a request is sent on an idle connection at the same moment that the server decides to send close_notify and drop the connection.