I have read in many places that theoretically connecting to ssl / 443 websocket has a high percentage success rate when the client is behind corporate proxies / firewalls. This topic also addresses the issue: Web sites behind enterprise proxies .
Our node.js setup with the websocket-node server that transfers binary data to the Chrome 15+ client. No performance issues as it flashes quickly. However, I have unsuccessful connections within corporations, in one example I know that they use an explicit proxy server connecting to this proxy server on port 8080.
The first question is two parts: a) what mechanisms can I use to debug the problem, to know what blocks the update, and b) for those who have experience, which is most likely the culprit?
Secondly, what performance will hit if I go back to flash (i.e. websocket-js)?
Thank you very much in advance.
UPDATE: Now it’s clear that the confirmation request is never viewed by the websocket server, so it is blocked on the client side before the request ever leaves.
source share