https://bz.apache.org/bugzilla/show_bug.cgi?id=57795
--- Comment #7 from Gaël Oberson <[email protected]> --- It's exactly what I point out. An IOS Chrome or Safari may be killed (just swipe up) by the user. In that case, je JavaScript thread is instantly terminated, and thus the SockJS client has no chance to close() the socket. Therefore, Apache needs to handle this and become the ability to "be aware" that the client just went away. If you run this scenario without Apache, and directly use Tomcat, you will see that Tomcat has this ability. When the IOS Browser is killed, Tomcat closes the Socket immediately and releases the resources. Thus, it should be possible for mod_proxy_wstunnel to do the same. Otherwise, this will lead to a ressource leak. -- 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]
