Re: Can't omit port number using server directive...

2012-06-27 Thread Willy Tarreau
Hi Chris, On Wed, Jun 27, 2012 at 12:57:48AM -0500, Chris LeBlanc wrote: Hi friends, I'm trying to allow nginx to delegate https properly and one way I see to prevent from having to write a bunch of backends in haproxy is to omit the port number when using the server directive as follows:

Re: Can't omit port number using server directive...

2012-06-27 Thread Chris LeBlanc
Thanks Willy. One last couple of questions. Can I check both ports or would I need to still write two backends? If I have to use two backends are th cookies shared? i.e. if someone logs in using https and switches to http would they still remain stuck on the same server? On Jun 27, 2012, at

Re: Can't omit port number using server directive...

2012-06-27 Thread Baptiste
Hi, A single cookie name can be used in two farms, if you keep the same name and cookie value for the server and if SSL offloading is done before HAProxy. You can't check 2 ports in HAProxy, there are some dirty work arounds like using a single backend to monitor all the ports on your server.

Can't omit port number using server directive...

2012-06-26 Thread Chris LeBlanc
Hi friends, I'm trying to allow nginx to delegate https properly and one way I see to prevent from having to write a bunch of backends in haproxy is to omit the port number when using the server directive as follows: frontend https bind :81 accept-proxy maxconn 1