WSS Server: succeeded firstly then failed afterwards with chrome/IOS

[jiangjianping]

We are running this wss server under android. There is no any problem to connect with this server using wss client under android. The wss client of chrome can also work with this server firstly. But if we close the wss connection and connect with this WSS server again, it failed mostly. We found that the chrome omitted the "Client Key Exchange..." after the first established connection. The IOS websocket client had the same problem.

[PhilipRoman]

Can you provide some code or application which reproduces this issue?

[jiangjianping]

Hello,
I attached the packet captured by wireshark. In my opinion, The server may tell the client it can cache the session(key), but the time is very short. The connection created by chrome had "client key exchange..." firstly, then we close this connection and open the websocket connection with wss server again, the "client key exchange..." missed.

[jiangjianping]

the code we use is just the SSLServerExample.java. The problem is due to session reuse.

[jiangjianping]

We patched with the code from #943 , It seemed that the problem was solved. It is reasonable that the chrome not use False Start firstly, but session reuse will have the same effect as " False Fast" afterwards.

I appear to be experiencing the same issue as you. Implenting the bug fix you linked to has appeared to significantly reduce the number of failed connections, but I still do occasionally have issues whenever I restart the server. Totally ballparking here: I'd say before that bug fix, I'd experience issues 4/5 times, but afterward it's closer to 1/10 times. I can't really contribute any solutions or possible reasons as to what could be causing the issue, but figured I'd mention it at the very least.

[junaidnom]

I'm having similar issues. Not sure what it is.

Also the issue NEVER occurs when I use a java client, only JS client with browser.

Edit I found I got this error: The connection was closed because the other endpoint did not respond with a pong in time. For more information check: https://github.com/TooTallNate/Java-WebSocket/wiki/Lost-connection-detection
After onOpen is called.

[marci4]

@junaidnom you should report this error to the developer of the other endpoint.
The response to a ping is required by the specification!

Best regards,
Marcel

[marci4]

Closing issue as it was solved with #943