Correct. If the client expects TLS you will get an error if connecting to a plaintext server. Some languages may provide more error information than others, but in all language that information is intended for developers, not programs to inspect.
On Thu, Jun 13, 2019 at 12:00 PM Dave Quigley <dquig...@gmail.com> wrote: > Hello, > > I have enabled TLS between a gRPC client and server and require client > auth to be done as part of the exchange. I also have a flag to say that the > server should be started without TLS securing the channel. However there > does not seem to be a good way to figure out when connecting from a client > that expects a TLS handshake that the reason it was unable to connect is > that there is a mismatch of expectations. Am I missing something here? It > seems that TLS handshake failures are just treated as transient failures > and there is no way to get more details. > > Dave > > -- > You received this message because you are subscribed to the Google Groups " > grpc.io" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to grpc-io+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/grpc-io/f4429762-f894-42df-99a1-f7bdd5301390%40googlegroups.com > <https://groups.google.com/d/msgid/grpc-io/f4429762-f894-42df-99a1-f7bdd5301390%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CA%2B4M1oOao%3D26LHnG8BsErMrHQzXtmYP3O__2HYUju50%2BqynLPg%40mail.gmail.com.
smime.p7s
Description: S/MIME Cryptographic Signature
