> So is the only solution that's going to keep the connecting IP going to be using Apache for load balancing and SSL termination?
No, another solution is HAProxy for balancing and stud for termination. This combination is by far better, if you expect thousands of connections. On Sunday, August 12, 2012 3:24:44 PM UTC+2, Matt Sergeant wrote: > > So is the only solution that's going to keep the connecting IP going to be > using Apache for load balancing and SSL termination? It sounds like there's > still no good solution to this. > > Matt. > > On Fri, Aug 10, 2012 at 11:05 PM, Guillermo Rauch > <[email protected]<javascript:> > > wrote: > >> That's what I was clarifying. In reality it doesn't really *support* the >> WebSocket *protocol*, and that's why it can't add the X-Forwarded-For. >> It supports it in the same way it supports _any other_ protocol in TCP >> mode (like XMPP), just forward the traffic along. >> >> -- >> Guillermo Rauch >> LearnBoost CTO >> http://devthought.com >> >> -- >> 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]<javascript:> >> To unsubscribe from this group, send email to >> [email protected] <javascript:> >> 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
