rustls | A modern TLS library in Rust | TLS library

awc 2.0.3 requires rustls 0.18.1, as you can see by following the link to the ClientConfig in the documentation. You are, however, trying to use rustls 0.20.1. From the compiler's point of view, these two versions are two distinct, totally independent crates, and the types inside them, even if they are defined exactly the same, are incompatible with each other.

The solution therefore is simple - change version of rustls in your Cargo.toml to the one accepted by awc, i.e. 0.18.1.

The type mismatch occurred exactly in accordance to the requested types declared. Looking again at the definition of client:

Thanks to @HHK in the comments above.

He recommended to build a minimal, reproducible example. While doing that, the example worked fine.

So I iteratively added the code from the original project around it.

The last step I added was a relic I did not remove when making the project async and learning about async.

I had a futures::block_on call within an async function calling an async function which resulted in blocking the whole program randomly.

So I should have made a full working piece of code before posting which would have lead me to the original problem an saved me a lot of headache.

For the future reader:

The modules client and stream are private, but client::ClientSession and stream::Stream are both exported by the rustls crate at the top level. You should be able to just write this as:

Is this the correct behavior for this example code?

Yes. This can also be checked when trying the same kind of request using other tools:

I cannot build your simplified Dockerfile as-is because I do not have the source files you reference in COPY statements, so I get "COPY failed" errors. You say "Building and running a new cargo default project with the x86_64-unknown-linux-musl target works" and indeed this Dockerfile (your simplified Dockerfile with the COPY commands removed) works fine for me:

As your error message describes, there's a trait AsyncReadExt that's implemented for the type, but not imported into scope. To be able to use the read method of that trait, you need to import the trait; for this trait, this is typically done by importing the tokio prelude:

It looks like your problem is not with Hyper or Rust, it is with TLS. By default, when you establish connection via HTTPS, client verifies server certificate authenticity. The certificate needs to be signed by a trusted authority: for details, see, for example, this page.

To verify, use curl:

Use StreamOwned instead: