Is it possible to configure port 80 on a Cisco load balancer as being general TCP, rather than specifically HTTP, in order to support more protocols on that port?
I am attempting to get Websockets working through the balancer but see behaviour suggesting it prevents non-HTTP traffic on port 80 by default.
I am to be load balancing two node.js/Socket.io instances on different boxes with nginx running a simple notifications service with a retroactive event for new clients.
I don't think there will be any issues with the websocket connection type (which will be the primary method of connection) as the maintained connection negates the need for a session (apart from on a reconnect which doesn't worry me too much).
However there will be a problem with the polling fallback approaches as they rely on client sessions and with standard roundrobin load balancing there's (in this case) a 50% chance the next poll will come up as a new client.
Rather than syncing the sessions across the two boxes, it makes sense to me to have the load balancer do some semi-intelligent routing using either the ip_hash directive or nginx-sticky-module.
ip_hash seems like it'd do the job but I can see it having potential issues with mobile clients who either swap IP addresses whilst on 3G or that change between the mobile network and WiFi thus changing IP address.
I have a couple of questions tied in with this; if you can answer either that'd be great...