-
Notifications
You must be signed in to change notification settings - Fork 504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gRPC interop: TLS problems #896
Labels
Comments
olix0r
added a commit
that referenced
this issue
Jan 11, 2017
Problem Finagle doesn't expose any way for clients to configure ALPN protocol negotiation. This breaks HTTP/2 clients. Solution Expose a new stack param, Netty4ClientTls.ApplicationProtocols. This parameter is used by the Netty4ClientTls channel handler, which is responsible for replacing the "ssl" and "sslConnect" channel handlers installed by com.twitter.finagle.netty4.ssl.Netty4SslHandler. We'll need to find a better long-term solution in Finagle. Fixes #760 Maybe #896 too
This looks like a problem with your certs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While trying to use linkerd as proxy for the grpc-java interop tests, I'm running into a TLS handshake error
linkerd logs:
client logs
The text was updated successfully, but these errors were encountered: