Hi, Are you sure your backend server is able to process IPv6 address in headers? Could you provide HAProxy logs showing the 502?
Regards On Fri, Sep 28, 2012 at 1:07 PM, [email protected] <[email protected]> wrote: > Hi folks, > > at the moment I'm testing IPv6 with HAProxy ("IPv6-to-IPv4-Translation"). > > Unfortunately IPv6-to-IPv4 HTTP-Connection doesn't work if you have "option > forwardfor" in your IPv6-Frontend. > (produces 502 errors on every connection). > > > If I remove "option forwardfor" from the IPv6-Frontend ("http_in_v6") it is > working as expected. > > > Unfortunately our application behind HAProxy uses X-Forward-For - header for > different functions and also HTTP-Request-Logging is affected (Apache > Access-Log + mod_rpaf, only HAProxy-IP is now logged on IPv6-Requests > instead of the real client ip). > > > Ubuntu 12.04 amd64, haproxy 1.4.22 > > > haproxy.cfg : > > > global > log 127.0.0.1 local0 > log 127.0.0.1 local1 notice > maxconn 20000 > ulimit-n 65536 > user haproxy > group haproxy > daemon > stats socket /var/run/haproxy.sock mode 0600 level admin > > > defaults > log global > mode http > option httplog > option dontlognull > retries 3 > option redispatch > maxconn 19500 > timeout connect 10s > timeout client 60s > timeout server 60s > timeout queue 60s > > > frontend http_in_v6 > bind 2001:XXX:XXX:37::9:80 > > reqidel ^X-Forwarded-For:.* > option forwardfor > > option http-server-close > > default_backend apache > > > > frontend http_in > bind 81.x.x.x:80 > > reqidel ^X-Forwarded-For:.* > option forwardfor > > option http-server-close > > default_backend apache > > > > backend apache > balance roundrobin > > appsession PHPSESSID len 64 timeout 3h request-learn prefix > > option httpchk GET /health.php HTTP/1.0\r\nUser-Agent:\ HAProxy > http-check expect status 200 > > server apache09 192.168.3.109:80 check inter 10000 rise 2 fall 2 maxconn > 250 weight 50 > >
