Can't recognize websocket "wss://" scheme

[yunkai]

SwitchyOmega can't recognize websocket "wss://" scheme when I access https://web.whatsapp.com (which will access wss://web.whatsapp.com), although I have all ready added a "*.whatsapp.com" into switch rules.

SwitchyOmega 2.5.20 Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36

[Checkroth]

I have a similar issue.

I understand that websocket schemes aren't supported because you simply can't proxy a websocket connection like you can HTTP/HTTPS.

However, I am in a situation where I want to use SwitchyOmega to simulate restrictive environments that have a man-in-the-middle filter and proxy (government institutions, schools, etc.). In order to simulate an environment where websockets don't work due to a network-level filter that the user has no control over, I attempted to set up SwitchyOmega funnelling all traffic through a mtim transparent proxy. Unfortunately this doesn't work, but I would like for the option.

[javabrett]

Proxying and proxy-switching with secure-websockets (wss://) protocol upgrades is working for me:

• Version 85.0.4183.83 (Official Build) (64-bit) MacOS Catalina
• SwitchyOmega Version 2.5.21

... with one big caveat: I needed to ensure that my proxy was activated for (default) scheme - for other traffic it was sufficient to proxy for https:// and have DIRECT for everything else, but this seems to not match after the protocol upgrade to wss://, so I had to enable default. This isn't too much of a problem for my use case, and I'm using it in combination with an auto-switch to select that proxy server.

[azatsh]

Same issue for me when connecting to telegram web. I think we need to have protocol WSS to be added in SwithcyOmega settings.

[rtunazzz]

Hey, facing the same issue.

Was anyone able to find a workaround?

[huangkaoya]

me too

[leowest77]

unhappily they don't seem to be interested in working this out...