Re: redispatch still cause error response

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 >To: flamese...@yahoo.co.jp >Cc: "haproxy@formilux.org" >D

Configuring HAproxy to Mbed tls implementation of TLS

Hello dear HAproxy stuff How can I configure HAproxy to a specific implementation of TLS, I mean for example " Mbed TLS" which is a security library dedicated to the embedded systems. Thanks in advance Mariam Abboush

Re: haproxy http2 benchmark

Hi, On Wed, Jan 31, 2018 at 10:41:44AM +0800, ??? wrote: > *hi all,* > *recently we are ready to upgrade to haproxy 1.8,however, when testing > HTTP2, we found a drop in performance,below is the test scenario:* (...) > *Use h2load test, respectively, test http1.1 and http2, A total of three >

Re: redispatch still cause error response

Hello, On 31 January 2018 at 03:00, 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

Re: redispatch still cause error response

Hi, Le 31/01/2018 à 03:00, flamese...@yahoo.co.jp a écrit : Hello, What exactly does option redispatch do? It gives a chance to retry on another server if the connection can't be established on the one chosen by the loadbalancing algorithm. It's important to understand that it concerns only