Jacob Hoffman-Andrews

I think actually curl passes through the ISO-8859-1 bytes unchanged, but my terminal turns those into [� Unicode Character 'REPLACEMENT CHARACTER' (U+FFFD)](https://www.fileformat.info/info/unicode/char/fffd/index.htm). Here's a screenshot of part of the output...

I think it would be hard to provide a Certificate object in a way that abstracts over native-tls, rustls, and mbedtls, since they each have their own internal way of...

I gave some feedback on #510, which seems like a good approach. Would you still like me to look at this implementation?

An interesting idea! One thing to note is that `Request` is actually a builder-style object. At `send()`, we build it into an internal-only object (currently called `Unit`, but could just...

Ah, this is a good point - I was thinking of this mainly in the context of printing the debug format of a URL directly, like `println!("{}", url)`. For the...

Users of `Uri` can't `#[derive(Debug)]` on it themselves if they want the split-out view, but they can use `format("{}", uri)` if they want the serialized view, so offering a split-out...

Related issue for Go: https://github.com/golang/go/issues/46287

> we probably want a different crate that provides implementations of rustls::ServerCertVerifier (to start) backed by the windows and mac verifiers. Is there a particular reason to do this as...

> Given that ServerCertVerifier is guarded with dangerous_configuration on the rustls side, there is some conflict between exposing a public implementation of the trait in a different crate while maintaining...

Aha, I was imagining that it would be up to the user to enable the dangerous_configuration flag. But we don't want users to have to enable that flag just to...