Netty WebSocket SSL连接HANDSHAKE_ISSUED
[英]Netty websocket SSL connection HANDSHAKE_ISSUED
问题描述
I got problem with netty websocket connection while handshaking with server. 
与服务器握手时，netty websocket连接出现问题。
I am using it on Android. 我在Android上使用它。
I got event SslHandshakeStateEvent.HANDSHAKE_ISSUED . 我收到了事件SslHandshakeStateEvent.HANDSHAKE_ISSUED 。
What I could read is that: 我能读的是：
The Handshake was started but the server did not response yet to the request . The Handshake was started but the server did not response yet to the request 。
Soon I got channelInactive and connection is closing. 很快我得到channelInactive并且连接关闭。
Looks like server problem, but connection to this server works fine on other platforms such as IOS, Windows, also it works fine with other servers. 看起来像服务器问题，但与此服务器的连接在IOS，Windows等其他平台上也能正常工作，在其他服务器上也能正常工作。
My question is that what could be wrong with this connection that I got HANDSHAKE_ISSUED, in what cases will these happen? 我的问题是，我得到HANDSHAKE_ISSUED的连接有什么问题，在什么情况下会发生？
EDIT Logs from netty, need to change adresses for xxx: 来自netty的EDIT日志，需要更改xxx的地址：
03-29 17:10:01.294 27227-27604/com.x.androidtestapp D/nativeSSL: [id: 0x3a098404] REGISTERED
03-29 17:10:01.294 27227-27604/com.x.androidtestapp D/nativeSSL: [id: 0x3a098404] CONNECT: xxx/xxx
03-29 17:10:01.594 27227-27604/com.x.androidtestapp D/nativeSSL: [id: 0x3a098404, /xxx => xxx] ACTIVE
03-29 17:10:01.604 27227-27604/com.x.androidtestapp D/nativeSSL: [id: 0x3a098404, /xxx => xxx] WRITE, DefaultFullHttpRequest(decodeResult: success)
03-29 17:10:01.604 27227-27604/com.x.androidtestapp D/nativeSSL: GET /notification/notificationChannel/websocket HTTP/1.1
03-29 17:10:01.604 27227-27604/com.x.androidtestapp D/nativeSSL: Upgrade: websocket
03-29 17:10:01.604 27227-27604/com.x.androidtestapp D/nativeSSL: Connection: Upgrade
03-29 17:10:01.604 27227-27604/com.x.androidtestapp D/nativeSSL: Sec-WebSocket-Key: K4zSElkfuBKi6ymQ1VVhuw==
03-29 17:10:01.604 27227-27604/com.x.androidtestapp D/nativeSSL: Host: xxx
03-29 17:10:01.604 27227-27604/com.x.androidtestapp D/nativeSSL: Sec-WebSocket-Origin: http://xxx
03-29 17:10:01.604 27227-27604/com.x.androidtestapp D/nativeSSL: Sec-WebSocket-Version: 13, 0B
03-29 17:10:01.604 27227-27604/com.x.androidtestapp D/nativeSSL: [id: 0x3a098404, /xxx => xxx/xxx] FLUSH
03-29 17:10:02.575 27227-27604/com.x.androidtestapp D/nativeSSL: [id: 0x3a098404, /xxx :> xxx/xxx] UNREGISTERED
1 个解决方案
解决方案1
0 2018-06-05 21:44:47
握手的http部分有未处理的401。
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.