On Fri, Jun 10, 2016 at 7:39 PM, Kevin Maziere <ke...@kbrwadventure.com> wrote:
> Hi > (in english this time,sorry for the noise) > > I can't explain a strange behavior of haproxy when using simple acl which > redirect to a specific backend. > The frontend in which the ACL and the specific backend is set has also a > default frontend. > > If I curl/wget/chrome/firefox/opera... on the frontend IP with a hostname > which match the ACL, sometime the reply is made by the wanted backend, > sometime by the default one,randomly. > And the request you are testing with is??? > No error logs > If I remove the default backend line, all request are sent to the specific > backend. > > Any help ? > > Tanks > > Kévin > > > Here is my conf : > > global > log 127.0.0.1 local0 > log 127.0.0.1 local1 notice > maxconn xxxxx > #debug > #quiet > #spread-checks > user haproxy > group haproxy > defaults > log global > mode http > #option dontlognull > maxconn xxxx > timeout server xxm > timeout connect xxm > timeout client xxm > option redispatch > retries 5 > option httplog > option forwardfor > timeout http-keep-alive xm > timeout http-request xm > > > frontend 10.0.01-80 > bind 10.0.0.1:80 > reqadd X-Forwarded-Proto:\ http > option http-server-close > > acl host_beg_ttfr hdr_beg(Host) tt-fra29-2-france > use_backend tt-france-fra29-2 if host_beg_ttfr > > default_backend ipv4-fr > > backend tt-france-fra29-2 > reqirep ^Host:\ tt-france-fra29-2-france.subd.fr.mondomainamoi.fr > Host:\ fra29-2-fra.md.bbb.loca > server labas 192.168.21.5:80 > > backend ipv4-fr > balance roundrobin > option httpchk GET / > server fr-icietla 192.168.22.4:8080 weight 1 check inter 5000 rise 2 > fall 5 > -- Igor Cicimov | DevOps p. +61 (0) 433 078 728 e. ig...@encompasscorporation.com <http://encompasscorporation.com/> w*.* www.encompasscorporation.com a. Level 4, 65 York Street, Sydney 2000
