| commit | 8e0d2bda09608986d880fa72fe163d1277a06b76 | [log] [tgz] |
|---|---|---|
| author | Inna Palant <[email protected]> | Wed Jun 12 11:13:24 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Wed Jun 12 11:13:24 2024 +0000 |
| tree | 743ee14d9d7959e158ba87e0a8d2e31d36162279 | |
| parent | d9ee44c999ed81680934585e2113ef4791073db7 [diff] | |
| parent | 96a2e67c681216e05f138c856e7d5f03397eff40 [diff] |
Merge remote-tracking branch 'origin/upstream' am: 01030d454c am: 96a2e67c68 Original change: undetermined Change-Id: Ida3a510bcd24179ea5534e03611d3066906ee749 Signed-off-by: Automerger Merge Worker <[email protected]>
A connect, read and write timeout aware connector to be used with hyper Client.
At the time this crate was created, hyper does not support timeouts. There is a way to do general timeouts, but no easy way to get connect, read and write specific timeouts.
There is a TimeoutConnector that implements the hyper::Connect trait. This connector wraps around HttpConnector or HttpsConnector values and provides timeouts.
Note: In hyper 0.11, a read or write timeout will return a broken pipe error because of the way tokio_proto::ClientProto works
Hyper version compatibility:
master branch will track on going development for hyper.0.4 release supports hyper 0.14.0.3 release supports hyper 0.13.0.2 release supports hyper 0.12.0.1 release supports hyper 0.11.Assuming you are using hyper 0.14, add this to your Cargo.toml:
[dependencies] hyper-timeout = "0.4"
See the client example for a working example.
Licensed under either of
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.