Also be aware that hyper/reqwest will happily run out of system connections if you're not careful. What happens is that the client has a connection pool but idle connections are not necessarily closed immediately. Even with only a single concurrent connection, when you try to reuse the same connection pool to access thousands of different domains, the pool might keep connections open since there is no max number of connections per pool limit. Some details: Hyper not cleaning up idle connection...
This seems to be a 1 year old bug that appears to be already fixed, am I missing something?
Oh, I didn’t know that. Thank you!
I’m not entirely sure about it, but this issue: https://github.com/hyperium/hyper/issues/2420 and this linked one: https://github.com/seanmonstar/reqwest/issues/1162 seem to be resolved.