I have a similar interest. I'd love to see the full config that you have come up with.
LES Sent from my iPad On Mar 15, 2011, at 6:07 PM, "Shaw, Christopher" <[email protected]> wrote: > Willy, > > Thanks for the reply. We are attempting to use an ACL to (1) > test for the existence of an RDP cookie using "acl <rulename> > req_rdp_cookie_cnt gt 0" and then (2) use the "force-persist if > <rulename>" statement. Our end goal is to make sure that if a user has > an existing session on a server that was removed from the pool (for > failing a server health check) they can still reconnect to said session. > We are using TCP mode, not HTTP mode, so I wasn't sure if using the > force-persist statement was feasible in this fashion. > > > -----Original Message----- > From: Willy Tarreau [mailto:[email protected]] > Sent: Tuesday, March 15, 2011 5:28 PM > To: Shaw, Christopher > Cc: [email protected] > Subject: Re: Question about using "force-persist" > > On Mon, Mar 14, 2011 at 02:18:36PM -0500, Shaw, Christopher wrote: >> We are attempting to implement a "force-persist" rule using HAProxy, >> but aren't having much success. Is the "force-persist" option >> available to be used with TCP connections? > > How are you trying to use it ? There are very little information here, > could you please post an example of a config featuring the option and an > example of what you'd like it to work in your case ? > > Normally it's just HTTP, but the principle is that if a stickiness > information is identified in a request, and the force-persist rule > matches, then it should be forced to the server whatever its apparent > state. So that should work with TCP stick-tables in theory. > > 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. > >
