On 8 May 2012 20:24, Emmanuel Bézagu <[email protected]> wrote: > > you're right but this works only with a single protocol managed by haproxy, > doesn't it ? > My idea was to have an ACL for each of these standard protocols in order to > have a specific backend.
1) That's why there are different ports for different protocols; just put haproxy on each protocol's native port; 2) MY EYES THEY BURN! Seriously, Comic Sans when posting to mailing lists? Didn't your mother teach you /any/ manners? ;-) J > 2012/5/7 Willy Tarreau <[email protected]> >> >> Hi Emmanuel, >> >> On Fri, Apr 20, 2012 at 09:02:07AM +0200, Emmanuel Bézagu wrote: >> > As haproxy already accepts to reverse proxy ssl and ssh, would it be >> > possible to support protocols as OpenVPN, tinc or XMPP ? >> >> Haproxy will work with any TCP-based protocol which does not report >> addresses or ports inside the payload. For instance, it works well >> on SSH, SMTP, LDAP, RDP, PeSIT, SSL, etc... but not on FTP, most RPC, >> etc... In general, any protocol which can easily be translated will >> work. I think this is the case for all those above, but you might >> prefer testing to be sure. >> >> Regards, >> Willy >> > -- Jonathan Matthews Oxford, London, UK http://www.jpluscplusm.com/contact.html
