You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2015/05/18 21:46:14 UTC
[Bug 57795] mod_proxy_wstunnel sometimes does not connect and
sometimes does not disconnect
https://bz.apache.org/bugzilla/show_bug.cgi?id=57795
Gaël Oberson <ga...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
Priority|P2 |P1
Severity|normal |major
--- Comment #2 from Gaël Oberson <ga...@gmail.com> ---
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: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org