You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At least when the URL scheme is http, no log is made of the request or its body.
At least when the URL scheme is https, the request correctly appears in the program log.
Minimal example to reproduce, with dependencies env_logger or stderrlog:
fnmain(){// stderrlog::new().verbosity(4).init().unwrap(); <- also tested with this logging backend (stderrlog), just in case.
env_logger::init();// RUST_LOG=tracelet c = reqwest::blocking::ClientBuilder::new().connection_verbose(true).build().unwrap();
c.get("https://ident.me").send().unwrap();
c.get("http://ident.me").send().unwrap();}
Huh, interesting. The connect file has a bunch of conditional stuff, so that we can support native-tls, rustls, both, neither, and proxies. It's possible one of those conditions forgets to wrap the socket?
At least when the URL scheme is
http
, no log is made of the request or its body.At least when the URL scheme is
https
, the request correctly appears in the program log.Minimal example to reproduce, with dependencies
env_logger
orstderrlog
:Output (abbreviated):
Output (full):
The text was updated successfully, but these errors were encountered: