Websockets 101
Encryption is not a panacea. As more websites use HTTPS, more corporate networks are installing content filters that passively filter HTTPS content.<p>Yes. I just said corporate networks are spying on HTTPS connections.<p>It's really simple to implement. Get some kind of web proxy that has support (Websense is pretty popular, amazingly) and generate a root cert on the box. Then use a group policy on your AD server to distribute the root cert to all the client systems. Now Websense can decode the HTTPS traffic by issuing its own fake certs to clients and handle the "real" HTTPS handshake on the frontend proxy side.<p>Result? Your websockets are still going to get fucked with by proxies. Can we please stop building fake protocols on top of real protocols now?