3 ms·
I can't speak to that vulnerability, but from what I have read websockets are more likely to not break on firewalls because they are using a well known port (ei
by danielrhodes 10y ago
I can't speak to that vulnerability, but from what I have read websockets are more likely to not break on firewalls because they are using a well known port (either 80 or 443). Websockets also start out looking like a standard HTTP request. Compared to say MQTT or another protocol which uses its own port, websockets don't require any special setup. However, that really only applies to encrypted websockets; unencrypted has been known to cause issues with older proxies.
- matthewaveryusa 10y agoFurthermore websockets mask the payload so that naive proxies that do deep packet inspection to find HTTP requests don't fall to the poisoned cache trap. http://security.stackexchange.com/questions/36930/how-does-websocket-frame-masking-protect-against-cache-poisoning http://security.stackexchange.com/questions/36930/how-does-w...
- stesch 10y agoA firewall is more than a port filter. Websockets don't use standard HTTP requests other than using standard ports. The header lines not mentioned in RFC 2616 get removed by a lot of corporate firewalls (that includes filtering proxies etc.).