https://bz.apache.org/bugzilla/show_bug.cgi?id=57795
Gaël Oberson <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- Priority|P2 |P1 Severity|normal |major --- Comment #2 from Gaël Oberson <[email protected]> --- Using Chrome or Safari on IOS, open a Websocket to Tomcat8 over Apache wstunnel (http connector). We use SockJS in an AngularJS WebApp, on iPad. If you normally close the browser's tab or if you kill (swipe up) the App, then the Javascript App will apparently not fire a websocket close(). In that case, the socket remains open forever between Apache and Tomcat. Apache does not 'see' that the client went away. Other browsers (on desktop OS's) are sending the close, but IOS (and perhap's Android??) not. In such a situation, the subsequent websockets handshakes are routed to this "half closed" socket, and we run into error and a not working XHR fallback. It just completely blocks the service. Running the same use case without Apache and working directly with Tomcat runs fine. Tomcat itself is capable to react to a 'disapeared' client and does close the websocket. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
