Hi list, I'm sorry if this question has already been asked but I don't see any answer to it. The backend servers already set a cookie which value identifies it (<random>.<server_id>)
Can haproxy archieve stickiness based on the <server_id> value ? Currently, I'm using cookie AUTH_SESSION_ID prefix server srv1 192.168.1.1 cookie s1 server srv2 192.168.1.2 cookie s2 but ending with <prefix>.<random>.<server_id> is redundant if I can make haproxy use <server_id> Thanks, Ionel -- 232 avenue Napoleon BONAPARTE 92500 RUEIL MALMAISON Capital EUR 219 300,00 - RCS Nanterre B 408 832 301 - TVA FR 09 408 832 301
