In Rust, libraries don't need to support timeouts themselves. Rust futures can be easily aborted, which means that every Future can be timed out externally. See tokio's timeout.
I think the goal is to disable the timeout behaviour.
Are you sure it is not your backend server that timed out?
What are these different environments? Is your hyper proxy or your backend server hosted behind some other proxy/load balancer? NGINX perhaps?
I'm asking, because I can't find any settings for connection timeouts in hyper either (neither for client or server). But a 60s timeout sounds suspiciously like the default timeout settings of the NGINX ingress controller, which cost me days trying to figure out why my server was timing out, even though I turned off any timeouts.
Reason found. the connection is terminated because Kubernetes Ingress drops the inbound connection and hence hyper terminates the service execution and hence the connecton to backend is also terminated. strange that it does not raise any error when inbound connection is terminated.