Willy,
I thought I had come up with a working config file, but the
server persistence still isn't behaving properly. If a server is down,
or has its weight dropped to 0, a user is unable to reconnect to their
session from a different IP -- which means that the RDP cookie
persistence is broken somewhere.
Here is what I have under the "listen" section of my HAProxy config. Is
there a specific order necessary for some of these directives? Or is
there something else that I'm missing? Any help would be greatly
appreciated.
==================
= HAProxy Config =
==================
mode tcp
log global
option persist
option redispatch
option tcpka
option tcplog
option httpchk
persist rdp-cookie
acl rcookie req_rdp_cookie_cnt gt 0
tcp-request inspect-delay 10s
tcp-request content accept if RDP_COOKIE
tcp-request content reject
balance rdp-cookie
hash-type consistent
==================
Thanks,
Chris
-----Original Message-----
From: Willy Tarreau [mailto:w...@1wt.eu]
Sent: Wednesday, March 16, 2011 3:50 PM
To: Shaw, Christopher
Cc: haproxy@formilux.org
Subject: Re: Question about using "force-persist"
On Wed, Mar 16, 2011 at 01:29:20PM -0500, Shaw, Christopher wrote:
> >From the HAProxy 1.4 documentation, I was under the impression that
> "option persist" was only for HTTP connections, not TCP connections.
> Is "option persist" available for both modes?
You're right, because option persist was added long before we would
support anything beyond HTTP. Yes, this option is supported on TCP.
Regards,
Willy
-----------------------------------------
The information contained in this e-mail message, and any attachment thereto,
is confidential and may not be disclosed without our express permission. If you
are not the intended recipient or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby notified that
you have received this message in error and that any review, dissemination,
distribution or copying of this message, or any attachment thereto, in whole or
in part, is strictly prohibited. If you have received this message in error,
please immediately notify us by telephone, fax or e-mail and delete the message
and all of its attachments. Thank you. Every effort is made to keep our network
free from viruses. You should, however, review this e-mail message, as well as
any attachment thereto, for viruses. We take no responsibility and have no
liability for any computer virus which may be transferred via this e-mail
message.
