Is it possible to analyze the TCP header and take action based on it with HAProxy 2.0? I want to place a magic number in the reserved fields of the TCP header on my backend and have HAProxy behave differently depending on it.

I have successfully configured HAProxy to load balance my sites, and it is working fine. However, I need assistance with blocking direct access to certain URLs such as example1.com, example2.com, and example3.com.

just need some help with my haproxy.cfg.

I’m about to test PostgreSQL connection idling over HAProxy. I let a JDBC connection idle in a loop to test this. With each iteration I am doubling the idle wait time.

I’m currently using “default_redirection_url” parameter in Authelia but it redirects the user at first login only, so is there any way to add a link or button for the user to click on when he is stuck in the user settings page?
I’ve integrated Authelia with HAProxy so I want to make sure that if a user manually browses to “https://sso.domain.com:9091/” for whatever reason, he will be able to find his way back to the actual backend application.

This is what the backend I want is like

I have a HAproxy instance with one backend and two mysql servers. My question is Can I set for each server in backend different healthchecks? It could be perfect to set mysql-check to backend server and tcp-check to main server. I didn’t find this in official docs.

I have a haproxy server to proxy requests to some node js web services. On node I want to detect when clients disconnects because I need to invalidate it’s requests on my Redis queue.
If I connect directly to my node server I can detect client disconnection, but if I pass through haproxy the clients seem to be always connected.
I suspect that haproxy does not propagates clients disconnection on server side.

i’m trying to deploy a docker swarm of two host nodes and two host manager with a single replicated service and put an haproxy in front of it. i want the clients to be able to connect via port 80.

Using haproxy I’m trying to secure website using basic auth+session cookie: