[英]Netty websocket SSL connection HANDSHAKE_ISSUED
與服務器握手時,netty websocket連接出現問題。
我在Android上使用它。
我收到了事件SslHandshakeStateEvent.HANDSHAKE_ISSUED
。
我能讀的是:
The Handshake was started but the server did not response yet to the request
。
很快我得到channelInactive
並且連接關閉。
看起來像服務器問題,但與此服務器的連接在IOS,Windows等其他平台上也能正常工作,在其他服務器上也能正常工作。
我的問題是,我得到HANDSHAKE_ISSUED的連接有什么問題,在什么情況下會發生?
來自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
握手的http部分有未處理的401。
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.