[ACCEPTED]-Will html5 websockets be crippled by firewalls?-portforwarding

Accepted answer
Score: 27

I'm not an expert (so please check to confirm) but 7 I believe there will be an UPGRADE mechanism 6 where a regular HTTP connection can be made, then 5 upgraded to a WebSocket, so no existing 4 firewall rules interfere unless they are 3 doing aggressive application level packet 2 inspection. Connections are still initiated 1 by the browser.

Score: 9

HTML 5 WebSockets don't require port forwarding. Connections 5 continue to be established from the client, but 4 the client and server asymmetry disappears 3 once the connection is established. WebSockets 2 also punch through proxies by using the 1 same CONNECT mechanism that HTTPS uses today.

Score: 7

Since firewalls typically simply enforce 7 the rules for inbound traffic rejection 6 and outbound traffic routing (usually through 5 the proxy server), there usually are no 4 specific WebSocket traffic-related firewall 3 concerns.

Proxy servers (and to some extent, certain 2 load balancing routers as well) are a different 1 matter though (See Why don't current websocket client implementations support proxies?)

More Related questions