IE11 Websocket Timeout
We are having an issue where IE11 will drop the WebSocket connection to Tigase if no information is sent across it for 30 seconds.
Upon further investigation we found that after 30 seconds IE11 is sending a 'WebSocket Pong' to Tigase. The packet, however, appears to be malformed or at least incorrect as it claims to have a payload but has nothing there. If there is no response IE11 assumes the server is no longer listening on the WebSocket connection if there is no response. Our assumption is that Tigase is holding on the payload that the packet claims is there and so it never responds and IE11 closes the connection.
We have found you can prevent this by sending out a packet every 25 seconds so that IE11 never issues the 30 second idle check but this is clearly sub optimal.
We are curious if anyone else has run into this issue and found a different way around it or if there is a way to modify Tigase such that it will respond to the packet despite its being malformed.
Added by Andrzej Wójcik over 4 years ago
We have not run into this issue, but we will investigate this issue as we will be working on new implementation of WebSocket compatible with new draft of specification for XMPP over WebSocket, see http://tools.ietf.org/html/draft-ietf-xmpp-websocket-06