websocket support for WAF
we are hosting a SignalR hub (http://signalr.net/) behind a Sophos UTM 320. We use the Web Server Protection feature extensively in our environment, and as such have opted to use the same for this.
SignalR will always try to use Web Sockets (http://en.wikipedia.org/wiki/WebSocket), a new HTML5 API, and fallback to other technologies where this isn't possible to be used.
Since we've been hosting the hub via the reverse proxy, none of our clients are able to connect via Web Sockets :so having support for websockets in WAF would be super cool
Stephen C commented
yup need this
Bad move not listening to your users Sophos. We are dropping UTM9 for this exact reason.
I shouldn't have to hack conf files to get this to work.
This is a basic requirement for a modern web applications, WebSockets have been around for years and years now. Heck, this "feature" request has been open for 2 years.
See this post on the bbs. It can be done, but every reboot of the UTM wipes it out.
It should be simple for Sophos to add this feature.
Are there any new informations? I´ve problems with websocket-Errors in combination of HTML5-VPN-UserPortal and WAF.
We also have the Requirement for allowing Web Sockets through WAF. We are hosting nodeJS Application wich also uses Web Sockets and falling down to an alternative connection takes to much time. Is there Any Solution on the way?
So UTM 9.3 now has apache 2.4.10 which includes the mod_proxy_wstunnel module. How about giving us a way to enable it!
This should be easy to do for Sophos as there is now a mod_proxy_wstunnel that provides this. Sophos just need to bump the version of apache they use to 2.4.5 or later (better to use 2.4.9) and allow for it in the configuration.