Well that worked. I didn't see any warnings before at startup no, but that may be because I use puppet to deploy my configurations and restart services as needed. Thanks for finding my simple mistake!
-----Original Message----- From: Aleksandar Lazic [mailto:[email protected]] Sent: Tuesday, August 15, 2017 10:04 AM To: Gibson, Brian (IMS) <[email protected]>; [email protected] Subject: Re: Problem getting cookies to work Hi Brian. Gibson, Brian (IMS) wrote on 15.08.2017: > I've been fighting with this a bit and I keep scratching my head. I > am trying to setup the VMware Horizon View UAG behind haproxy. It > requires session persistence, which I could do with a stick table, but > I'd rather use a cookie in case the load balancer goes down for > whatever reason, I have another using the same VIP and I want the > client to hit the same backend so long as it's up. > > Here's the configuration I tried most recently: > > listen vmview-uag > bind vip:443 ssl crt cert.pem > mode tcp I think you will need here mode http Doesn't you get any warning at startup time from haproxy? > balance roundrobin > cookie JSESSIONID prefix > option httpchk GET /favicon.ico HTTP/1.1 > > server vuag-01 10.10.10.1:443 ssl verify none cookie vuag-01 check > server vuag-02 10.10.10.2:443 ssl verify none cookie vuag-02 check > > JSESSIONID is provided by the UAG, when I use the above configuration > the cookie remains the same as if I don't do anything with it. I also > attempted to create a new cookie called SERVERID and no cookie shows up on > the client side. > > I'm using haproxy 1.7.2. Also I did double check that the ssl > certificate is the same on the UAG as the Haproxy, and according to > the VMware documentation this should be a supported configuration. -- Best Regards Aleks ________________________________ Information in this e-mail may be confidential. It is intended only for the addressee(s) identified above. If you are not the addressee(s), or an employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error.
