feature request: display stats

[luisdavim]

It would be nice to show some timing stats, something like httpstat

https://github.com/davecheney/httpstat

[ducaale]

Is there a particular stat you would be interested in? Currently, -vv displays the total duration, but we could also add time-to-first-byte and content-download duration.

For more granular stats, it would have to be supported in hyper/reqwest first.

• Controls for granular benchmarking hyperium/hyper#56
• Is it possible to get timing breakdown per request? seanmonstar/reqwest#1352

[ducaale]

From @blyxxyz in #347 (comment)

HTTPie issue: httpie/cli#1495

This is maybe something we could handle by printing debug logs. Some of our dependencies already generate logs through log but we don't have a way to show them right now. They don't include the IP address but we could add our own log message for that (if we can get that info at all).

If we go that route then we don't have to worry as much about what HTTPie does.

[blyxxyz]

We don't have a fancy chart but it's now possible to glean timing information from the --debug logging:

$ xh --debug https://example.org
[...]
[0.025361s DEBUG reqwest::connect] starting new connection: https://example.org/
[0.025569s DEBUG hyper_util::client::legacy::connect::dns] resolve; host=example.org
[0.045417s DEBUG hyper_util::client::legacy::connect::http] connecting to 23.215.0.132:443
[0.152797s DEBUG hyper_util::client::legacy::connect::http] connected to 23.215.0.132:443
[...]
[0.359712s DEBUG rustls::client::hs] ALPN protocol is Some(b"h2")
[...]
[0.489895s DEBUG h2::codec::framed_read] received frame=Headers { stream_id: StreamId(1), flags: (0x4: END_HEADERS) }
[0.489930s DEBUG h2::codec::framed_read] received frame=Data { stream_id: StreamId(1), flags: (0x1: END_STREAM) }
[...]