We have a web server that sends websocket requests when being accessed. We are able to make it work through HTTP traffic, but when we got an SSL certificate to make it HTTPS, the websocket requests fails.
I have tried using Path-Specific Routing to enable the Websocket Passthrough but it still doesn't work. Am I just not using the Path-Specific Routing correctly or is it a limitation of Sophos for this case?
Hi Jason,Thank you for your query, did you first enable "Path-specific routing" then edit the default "/" path and toggle the "WebSocket passthrough" option ?------------
Thanks & Regards,
Vivek Jagad | Technical Account Manager 3 | Cyber Security EvolvedSophos Community | Product Documentation | Sophos Techvids | SMSIf a post solves your question please use the 'Verify Answer' button.
Yes, I enabled path-specific routing first. I'm just not sure what to put on the path.
If my domain is redirecting to https://example.com/kto/lib/game, should I put /kto/lib/game on the path?
Yes, you can put such /kto/lib/game that should be fine.REF: https://docs.sophos.com/nsg/sophos-firewall/19.0/Help/en-us/webhelp/onlinehelp/AdministratorHelp/RulesAndPolicies/WebServerProtection/WAF/Rules/WAFRuleAdd/index.htmlPoint 6. Path-specifc routing
The path was not working but when I turned it back to / only, the website loaded but the websocket is still getting blocked.
So is it Websocket connections to an external site. Blocked coming back in?
It is an internal site websocket connection. There is no issue when I'm testing it via HTTP. I didn't even use path-specific routing when testing HTTP and it still works.