java - javax.net.ssl.SSLException: Received fatal alert: unexpected_message -
encountered sslexception when using curl hit java web service:
javax.net.ssl.sslexception: received fatal alert: unexpected_message @ sun.security.ssl.alerts.getsslexception(alerts.java:208) ~[na:1.8.0_65] @ sun.security.ssl.sslengineimpl.fatal(sslengineimpl.java:1666) ~[na:1.8.0_65] @ sun.security.ssl.sslengineimpl.fatal(sslengineimpl.java:1634) ~[na:1.8.0_65] @ sun.security.ssl.sslengineimpl.recvalert(sslengineimpl.java:1800) ~[na:1.8.0_65] @ sun.security.ssl.sslengineimpl.readrecord(sslengineimpl.java:1083) ~[na:1.8.0_65] @ sun.security.ssl.sslengineimpl.readnetrecord(sslengineimpl.java:907) ~[na:1.8.0_65] @ sun.security.ssl.sslengineimpl.unwrap(sslengineimpl.java:781) ~[na:1.8.0_65] @ javax.net.ssl.sslengine.unwrap(sslengine.java:624) ~[na:1.8.0_65] @ org.jboss.netty.handler.ssl.sslhandler.unwrap(sslhandler.java:1225) ~[netty-3.6.6.final.jar:na] @ org.jboss.netty.handler.ssl.sslhandler.decode(sslhandler.java:913) ~[netty-3.6.6.final.jar:na] @ org.jboss.netty.handler.codec.frame.framedecoder.calldecode(framedecoder.java:425) ~[netty-3.6.6.final.jar:na] @ org.jboss.netty.handler.codec.frame.framedecoder.messagereceived(framedecoder.java:303) ~[netty-3.6.6.final.jar:na] @ org.jboss.netty.channel.channels.firemessagereceived(channels.java:268) ~[netty-3.6.6.final.jar:na] @ org.jboss.netty.channel.channels.firemessagereceived(channels.java:255) ~[netty-3.6.6.final.jar:na] @ org.jboss.netty.channel.socket.nio.nioworker.read(nioworker.java:88) ~[netty-3.6.6.final.jar:na] @ org.jboss.netty.channel.socket.nio.abstractnioworker.process(abstractnioworker.java:109) ~[netty-3.6.6.final.jar:na] @ org.jboss.netty.channel.socket.nio.abstractnioselector.run(abstractnioselector.java:312) ~[netty-3.6.6.final.jar:na] @ org.jboss.netty.channel.socket.nio.abstractnioworker.run(abstractnioworker.java:90) ~[netty-3.6.6.final.jar:na] @ org.jboss.netty.channel.socket.nio.nioworker.run(nioworker.java:178) ~[netty-3.6.6.final.jar:na] @ java.util.concurrent.threadpoolexecutor.runworker(threadpoolexecutor.java:1142) [na:1.8.0_65] @ java.util.concurrent.threadpoolexecutor$worker.run(threadpoolexecutor.java:617) [na:1.8.0_65] @ java.lang.thread.run(thread.java:745) [na:1.8.0_65]
curl output:
[team@pins ~]$ curl -v --data '' 'https://example.com:6521/access/register' * adding handle: conn: 0x7f857480bb00 * adding handle: send: 0 * adding handle: recv: 0 * curl_addhandletopipeline: length: 1 * - conn 0 (0x7f857480bb00) send_pipe: 1, recv_pipe: 0 * connect() example.com port 6521 (#0) * trying xxx.xxx.xxx.xxx... * connected example.com (xxx.xxx.xxx.xxx) port 6521 (#0) * unknown ssl protocol error in connection example.com:-9800 * closing connection 0 curl: (35) unknown ssl protocol error in connection example.com:-9800
strangely, same command works on machine older version of curl. there, appears working fine aes128-sha.
i suspect it's problem available ciphers sent during ssl negotiation, i'm unsure how debug that. there way see curl sent? or server received?
Comments
Post a Comment