There is a server on WebSocket (node.JS), everything works fine. The only time is that if a person visits the site "from a working computer" and tries to connect to the WebSocket server - the server falls off. It also falls off when trying to connect via ssl (the certificate is not self-signed). A regular user connects freely, yet who "from work" cannot.

I understand that corporate proxies in most cases are so sharpened, chop off everything that they do not know.
Question: is it possible to circumvent such bans (setting up nginx / connecting special modules, if any) so that when attempting to connect from corporate networks, the handshake went smoothly? Which way to dig? :)

    1 answer 1

    You can bypass almost any proxy using https (in the case of web sockets - wss). Only proxy servers that use certificate spoofing can interfere with encrypted traffic. But if the admin has managed to configure such a proxy, then he may well have the skills for web sockets.

    The solution that works in the general case is automatic fallback to long pooling in case of unavailability of web sockets.

    • As already mentioned: https / wss is being used, however, a few people still complain - they cannot come in from work. Probably still have to resort to options such as socket.io, although it did not want to. Thank you :) - hender