Dear Willy,
Thank you for the quick response. I wasn’t interested in some specific TCP option. I was interested in differentiation of HAProxy heartbeat handshakes from client request tcp handshakes while connecting to the backend server. So, allowing any option to be forwarded to backend server would do the trick. Up till now I have thought about using (A) transparent proxy mode, (B) separate IP for heartbeat and separate IP for client request or (C) separate port for heartbeat and separate list of ports for client reuqest. However, in option (A) it isn’t possible to load balance traffic from the same subnet, option (B) is the best option I have so far but it requires an additional IP to be allocated to HAProxy and option (C) would limit the number of concurrent connections per backend server. Regards, zaafar From: Willy Tarreau Sent: Sunday, August 02, 2015 4:14 PM To: zaafar.ta...@gmail.com Cc: haproxy@formilux.org Hello, On Sat, Aug 01, 2015 at 09:23:27AM +0000, zaafar.ta...@gmail.com wrote: > Hello, > > > If client send few additional TCP options (during TCP handshake) to haproxy > would HAPROXY respect those options and forward them to the backend server? > Is it possible to enable this feature from the configuration file? No it is not possible. HAProxy is a TCP proxy meaning that it uses two separate and independant TCP connections. The options you have on one side may not even be relevant to the other side (eg: MSS values, etc). What do you have in mind, is there a specific option you're interested in ? Regards, Willy