连接到WireMock

我得到神秘的SSL握手错误，当我尝试连接到WireMock调试SSL握手错误。普通的HTTP嘲笑工作正常。连接到WireMock

我打开--print-all-network-traffic，当我打电话openssl s_client -connect 127.0.0.1:443 -showcerts -status -state -debug这是我所看到的：

2017-07-08 23:36:55.881 Opened Socket[addr=/172.17.0.1,port=46404,localport=443] 
2017-07-08 23:36:55.886 Problem decoding network traffic 
java.nio.charset.MalformedInputException: Input length = 1 
    at java.nio.charset.CoderResult.throwException(CoderResult.java:281) 
    at java.nio.charset.CharsetDecoder.decode(CharsetDecoder.java:816) 
    at com.github.tomakehurst.wiremock.http.trafficlistener.ConsoleNotifyingWiremockNetworkTrafficListener.incoming(ConsoleNotifyingWiremockNetworkTrafficListener.java:25) 
    at com.github.tomakehurst.wiremock.jetty9.JettyHttpServer$NetworkTrafficListenerAdapter.incoming(JettyHttpServer.java:364) 
    at org.eclipse.jetty.io.NetworkTrafficSelectChannelEndPoint.notifyIncoming(NetworkTrafficSelectChannelEndPoint.java:125) 
    at org.eclipse.jetty.io.NetworkTrafficSelectChannelEndPoint.fill(NetworkTrafficSelectChannelEndPoint.java:48) 
    at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.fill(SslConnection.java:507) 
    at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:239) 
    at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) 
    at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) 
    at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) 
    at java.lang.Thread.run(Thread.java:748) 
2017-07-08 23:36:55.895 Closed Socket[addr=/172.17.0.1,port=46404,localport=443] 
2017-07-08 23:36:55.896 Closed Socket[addr=/172.17.0.1,port=46404,localport=443]

在哪里何去何从任何想法？

来源

2017-07-08 suite22

Java方面不说TLS。 – EJP

有关如何重新配置WireMock/Jetty @EJP的任何想法？我对Jetty不太了解，但是我从WireMock文档中得出的假设是，它应该在使用HTTPS运行时处理此问题。 – suite22

这就是你只给公共证书时的样子。

来源

2017-07-11 00:07:30 AnitKryst

你钉了它@anitkryst - 刚刚有一个队友在这里让我知道密钥库只有公钥。 – suite22

回答

相关问题