In a recent customer case we encountered a problem based on a Proxy PAC file explicitly filtering for "https:".
However, the GoTo app uses also WebSocket connections starting with "wss:"
Hence in this case audio and video connections could not be established.
So when designing PAC files, consider that you also have to allow for WebSockets (in a standard config for HTTPS Proxies this should be included by default)
For further details about Firewall and Proxy configuration, you may consult:
https://support.goto.com/meeting/help/minimal-firewall-settings-for-the-goto-app
cheers
Robert
Solved! Go to Solution.
The GoTo app uses also WebSocket connections starting with "wss:"
So when designing PAC files, consider that you also have to allow for WebSockets (in a standard config for HTTPS Proxies this should be included by default)
For further details about Firewall and Proxy configuration, you may consult:
https://support.goto.com/meeting/help/minimal-firewall-settings-for-the-goto-app
The GoTo app uses also WebSocket connections starting with "wss:"
So when designing PAC files, consider that you also have to allow for WebSockets (in a standard config for HTTPS Proxies this should be included by default)
For further details about Firewall and Proxy configuration, you may consult:
https://support.goto.com/meeting/help/minimal-firewall-settings-for-the-goto-app