@theK wrote:
hello i’m trying to setup haproxy where the session sticks to the backend server used by 443 connection. So the tcp ports use the same backend server that was used in the http/443 connection. Also, is there another way to assign a unique cooke/id for a client instead of using IP
frontend infoos-https
bind *:80
bind *:443 ssl crt /etc/haproxy/ssl.net.pem
redirect scheme https code 301 if !{ ssl_fc }
reqadd X-Forward-Proto:\ https
mode http
default_backend infoosfrontend infoos-http
bind *:555 bind *:1443 bind *:7443 bind *:8983 bind *:9200 bind *:9543 bind *:9680 bind *:29090 bind *:29091 bind *:29092 mode tcp
default_backend infoos2
backend infoos
balance roundrobin
mode http
default-server inter 2s rise 2 fall 10
stick on src table infoos2
cookie SERVERID insert indirect nocache
server infoos1 10.200.1.212 ssl verify none check port 443 cookie infoos1
server infoos2 10.200.1.211 ssl verify none check port 443 cookie infoos2backend infoos2
balance roundrobin
mode tcp
stick-table type ip size 500k expire 8h
stick on src
option tcplog
server infoos1 10.200.1.212 check port 443 cookie infoos1
server infoos2 10.200.1.211 check port 443 cookie infoos2
Posts: 1
Participants: 1