We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
这是一个国密双向认证的场景。参考 credentials_test 创建了一个grpc连接,客户端申请并配置了证书,请求发出后,报错rpc error: unavailable, connection closed. nginx也是国密的配置,日志显示 "PRI * HTTP/2.0" 400 163 "-" "-" "-"
使用的nginx是用tassl和openresty一起编后构建的镜像,部署在一个k8s环境里。
看上去和http2 connection preface 相关问题有关,但nginx切成非国密的配置,grpc连接的配置也改用非国密的tls,可以正常调通,nginx日志里显示是http2的连接。不清楚这个问题和gmsm grpc国密的配置有关。
http client国密配置的调用没有问题。
The text was updated successfully, but these errors were encountered:
修复的pr #163
Sorry, something went wrong.
No branches or pull requests
这是一个国密双向认证的场景。参考 credentials_test 创建了一个grpc连接,客户端申请并配置了证书,请求发出后,报错rpc error: unavailable, connection closed. nginx也是国密的配置,日志显示 "PRI * HTTP/2.0" 400 163 "-" "-" "-"
使用的nginx是用tassl和openresty一起编后构建的镜像,部署在一个k8s环境里。
看上去和http2 connection preface 相关问题有关,但nginx切成非国密的配置,grpc连接的配置也改用非国密的tls,可以正常调通,nginx日志里显示是http2的连接。不清楚这个问题和gmsm grpc国密的配置有关。
http client国密配置的调用没有问题。
The text was updated successfully, but these errors were encountered: