2
You're describing the normal and expected behavior of a connection proxied at Layer 4.
In TCP mode, HAProxy does very little or no inspection of the traffic, and certainly does not attempt to read HTTP headers. It just passes traffic. Until one end or the other disconnects, it just keeps passing traffic.
If you want such a connection balanced between servers,...
2
I use in general a different approach which is a bit more generic - network capture. In Linux you can use tcpdump, here is an example: tcpdump -w network_capture.pcap -i eth0. Then I open the capture in WireShark.
You can use WireShark directly if you have a GUI in Linux, MacOS, Windows, etc.
1
In frontend www-https in bind line add ssl before crt. Without ssl it works as plain HTTP.
So:
bind *:443 ssl crt /etc/haproxy/certs/www.example.com.pem
1
You could try this:
location / {
return 301 http://my-other-server/?client_ip=$remote_addr&$args;
}
This will assign the IP address. https://github.com/flant/nginx-http-rdns is a reverse DNS lookup module for nginx, which provides $rdns_hostname variable, which you can use instead of $remote_addr. However, you need to compile the module to your ...
1
In haproxy declaring acl twice actually means OR of those conditions, so this:
acl TEST-RDR hdr_dom(Host) -i www.test.com
acl TEST-RDR path_beg /access/signin
means Host = www.test.com OR path_beg /access/signin which keeps evaluating to true, because you redirect to the same domain, so https://www.test.com/ redirects to https://www.test.com/ and you get ...
Only top voted, non community-wiki answers of a minimum length are eligible
