Inform users that for an https connection they should enable tls related feature flags
Feature Request
Crates
I had an issue with the tonic's feature flags and the failer that happened when I missed a need to enable tls related feature flags.
Motivation
I'm a newbie with grpc, and at the very beginning there are a lot of confusing moving parts that should be coordinated even a single request. I spend hard time trying to figure out what I'm doing wrong with my attempt to connect to a api which is available only on an https uri.
I have got on my attempt was an unhelpful error: "Status { code: Unknown, message: "transport error", source: Some(tonic::transport::Error(Transport, hyper::Error(Io, Custom { kind: BrokenPipe, error: "stream closed because of a broken pipe" }))) }"
Only after a lot of experementations of different kind, when googling doesn't helped me at all, as well as the search through the issues, I finally understood that maybe I have to enable some editional feature flags. And, "tls" and "tls-roots" helped me.
Proposal
I believe there is a way to check if the tls feature flags are enabled or not if there is an "https" schema used for the URI. And if the flags are not enabled the error message may mention them.
Alternatives
As alternative the documentation might be updated to highlight the importance of the tls related feature flags for the HTTPS uris.
Call to action
If you ok with the request, in general, I can prepare the PR for it.
anything yet?