We don't go through nginx for that server - it's bound to a different IP. So we have basically a dual system setup:
IP1 has the main app server: Stud -> HAProxy in http mode -> Nginx -> Node IP2 has the socket.io server: Stud -> HAProxy in tcp mode -> Node The main app server has socket.io loaded so that it can deliver the socket.io.js javascript file to browsers, but the clients actually make the socket.io requests to the server on IP2. This setup requires haproxy 1.5 (still in dev) for the PROXY protocol support. We lose the IP address in the socket.io calls, but that's OK - we get to log it for the normal web requests, which are most of the data transfer for our app. Matt. On Thu, Aug 16, 2012 at 1:15 PM, dvbportal <[email protected]> wrote: > Great choice. BTW. Have you found a way to dynamically bypass nginx when > you detect an upgrade to a websocket connection? > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
