>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?
Thanks, Chris -----Original Message----- From: Willy Tarreau [mailto:w...@1wt.eu] Sent: Wednesday, March 16, 2011 1:47 AM To: Shaw, Christopher Cc: haproxy@formilux.org Subject: Re: Question about using "force-persist" On Tue, Mar 15, 2011 at 05:07:02PM -0500, Shaw, Christopher 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. OK then you don't need this force-persist ACL. Just use "option persist" and it will work. Force-persist is used to force the user to go to the server even if it's dead and does not respond. That's used for application deployment teams to be able to see the errors reported by faulty servers. "option persist" just ignores the dead server status, but if the connection fails to establish, it will be redispatched to another server, which is what you want for your users. By the way, I'm seeing that force-persist is not considered by RDP cookies. That's no big deal, we should just add it. 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.
