Received: by 10.236.191.70 with SMTP id f46mr13511671yhn.44.1343947206246;
        Thu, 02 Aug 2012 15:40:06 -0700 (PDT)
X-BeenThere: socket_io@googlegroups.com
Received: by 10.100.202.10 with SMTP id z10ls1131481anf.3.gmail; Thu, 02 Aug
 2012 15:39:58 -0700 (PDT)
Received: by 10.236.109.233 with SMTP id s69mr5777596yhg.11.1343947198528;
        Thu, 02 Aug 2012 15:39:58 -0700 (PDT)
Date: Thu, 2 Aug 2012 15:39:58 -0700 (PDT)
From: mgutz <mario.l.gutier...@gmail.com>
To: socket_io@googlegroups.com
Message-Id: <3fd11ad8-09c4-45d2-9bdf-8dea9c98413c@googlegroups.com>
In-Reply-To: <CAFRHQJF9psX3-u=qMxpcnpsLXgNGew1LoB5R3BcKYrR5G5f=vg@mail.gmail.com>
References: <CAGOR8-1_fyvTjmpeqmoKurZAV_GL-bQOoUmFD3xFFcQ3pdp9zQ@mail.gmail.com>
 <c2d39210-3cdc-40a7-83d5-91d3778cf985@googlegroups.com>
 <CAFRHQJF9psX3-u=qMxpcnpsLXgNGew1LoB5R3BcKYrR5G5f=vg@mail.gmail.com>
Subject: Re: HAProxy and nodeJs server using SocketIO
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_241_17928318.1343947198098"

------=_Part_241_17928318.1343947198098
Content-Type: multipart/alternative; 
	boundary="----=_Part_242_2441406.1343947198098"

------=_Part_242_2441406.1343947198098
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

We create chat rooms based on client's remote address. Our deploy=20
environment is close to this article, except we use stud since it performed=
=20
better.

http://www.darkcoding.net/software/proxy-socket-io-and-nginx-on-the-same-po=
rt-over-ssl/


On Wednesday, August 1, 2012 2:33:52 PM UTC-7, Arne de Bree wrote:
>
> Same can be achieved using stunnel for ssl termination (or AWS ELB's in=
=20
> TCPssl mode)
>
> Downside of all this is that you loose the Client IP. None of stud,=20
> stunnel or ELB in TCPssl mode will set the X-Forwarded-For, which caused =
me=20
> to fallback to xhr and jsonp polling transports and use regular HTTPS=20
> termination sollution.
>
> You also want to watch out if you need stickyness or not, when you need t=
o=20
> keep state in your Node.js server, and you have multiple of them. Keep so=
me=20
> kind of stickyness in sight, or you need to share state between your node=
s.
>
> Regards,
> Arne
> =EF=9C=AB
> =20

------=_Part_242_2441406.1343947198098
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

We create chat rooms based on client's remote address. Our deploy environme=
nt is close to this article, except we use stud since it performed better.<=
div><br></div><div>http://www.darkcoding.net/software/proxy-socket-io-and-n=
ginx-on-the-same-port-over-ssl/<br><div><br><div><br>On Wednesday, August 1=
, 2012 2:33:52 PM UTC-7, Arne de Bree wrote:<blockquote class=3D"gmail_quot=
e" style=3D"margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;paddin=
g-left: 1ex;">Same can be achieved using stunnel for ssl termination (or AW=
S ELB's in TCPssl mode)<div><br></div><div>Downside of all this is that you=
 loose the Client IP. None of stud, stunnel or ELB in TCPssl mode will set =
the X-Forwarded-For, which caused me to fallback to xhr and jsonp polling t=
ransports and use regular HTTPS termination sollution.</div>


<div><br></div><div>You also want to watch out if you need stickyness or no=
t, when you need to keep state in your Node.js server, and you have multipl=
e of them. Keep some kind of stickyness in sight, or you need to share stat=
e between your nodes.</div>


<div><br></div><div>Regards,</div><div>Arne<br><span dir=3D"ltr">=EF=9C=AB<=
/span><br>
</div>
</blockquote></div></div></div>
------=_Part_242_2441406.1343947198098--

------=_Part_241_17928318.1343947198098--