On Mon, Feb 16, 2009 at 12:14 PM, Tomasz Sterna wrote:
>> Use legacy ssl port 5223.
> And forget XMPP clients that do not know anything about pre-XMPP legacy
> SSL tunnel?
Either that, or invest in some decent ssl hardware that is capable of
starttls in various flavours (where xmpp in various fla
Dnia 2009-02-13, pią o godzinie 21:10 +0200, Norman Rasmussen pisze:
> > Is this even possible? Lets say we have ssl in a load balancer and a
> xmpp
> > server behind it. Sending a or is gonna confuse
> the LB.
>
> Use legacy ssl port 5223.
And forget XMPP clients that do not know anything abou
On Fri, Feb 13, 2009 at 9:12 PM, Kevin Smith wrote:
> On Fri, Feb 13, 2009 at 7:10 PM, Norman Rasmussen
> wrote:
>> On Fri, Feb 13, 2009 at 9:00 PM, Adi wrote:
>>> Is this even possible? Lets say we have ssl in a load balancer and a xmpp
>>> server behind it. Sending a or is gonna confuse the
On Fri, Feb 13, 2009 at 7:10 PM, Norman Rasmussen
wrote:
> On Fri, Feb 13, 2009 at 9:00 PM, Adi wrote:
>> Is this even possible? Lets say we have ssl in a load balancer and a xmpp
>> server behind it. Sending a or is gonna confuse the LB.
> Use legacy ssl port 5223.
That's not going to help th
On Fri, Feb 13, 2009 at 9:00 PM, Adi wrote:
> Is this even possible? Lets say we have ssl in a load balancer and a xmpp
> server behind it. Sending a or is gonna confuse the LB.
Use legacy ssl port 5223.
--
- Norman Rasmussen
- Email: nor...@rasmussen.co.za
- Home page: http://norman.rasmus
Is this even possible? Lets say we have ssl in a load balancer and a xmpp
server behind it. Sending a or is gonna confuse the LB.
--
Thanks,
Adi
___
JDev mailing list
Forum: http://www.jabberforum.org/forumdisplay.php?f=20
Info: http://mail.jabber.org
