Thanks for reply, any plan to support this requirement? If a backend server get killed when processing request, that haproxy re-forwarad the request to another backend server?
Thanks ----- Original Message ----- >From: Lukas Tribus <[email protected]> >To: [email protected] >Cc: "[email protected]" <[email protected]> >Date: 2018/1/31, Wed 17:24 >Subject: Re: redispatch still cause error response > >Hello, > >On 31 January 2018 at 03:00, <[email protected]> wrote: >> Hello, >> >> What exactly does option redispatch do? > > >As per the documentation: >http://cbonte.github.io/haproxy-dconv/1.7/configuration.html#4-option%20redispatch > >"In HTTP mode, if a server designated by a cookie is down, clients may >definitely stick to it because they cannot flush the cookie, so they >will not be able to access the service anymore. > >Specifying "option redispatch" will allow the proxy to break their >persistence and redistribute them to a working server." > > >This is about breaking cookie persistence. > > > >> I have a haproxy in front of two web servers, if one web server get killed >> when haproxy is forwarding a request to that server, >> >> will this request get re-forwarded to another server? > >No. Haproxy will never resend a HTTP request that has already been >sent. If you break a backend with in flight HTTP transactions, those >transactions are supposed to break with it and that' exactly what >haproxy does. > > > >Regards, >Lukas > > > >
