[ANNOUNCE] haproxy-1.9-dev11

Hi, HAProxy 1.9-dev11 was released on 2018/12/16. It added 146 new commits after version 1.9-dev10. I expected to release this week-end after running it on the haproxy.org servers, but some annoying issues faced in production took some time to get fixed and delayed the release. Things have been

Re: Setting a unique header per server in a backend

Don't forget the "X-" header prefix is deprecated: https://tools.ietf.org/html/rfc6648 Norman Branitsky On Dec 16, 2018, at 03:50, Willy Tarreau mailto:w...@1wt.eu>> wrote: Hi Sachin, On Sat, Dec 15, 2018 at 10:32:21PM +0530, Sachin Shetty wrote: Hi, We have a tricky requirement to set a

Re: HTTP/2 to backend server fails health check when 'option httpchk' set

On Sun, Dec 16, 2018 at 12:01:18PM +0100, Baptiste wrote: > I don't know H2 well, but can't we forge an HTTP/2 query using tcp-check > script? Yes you can but you can't predict the result :-) Willy

Re: HTTP/2 to backend server fails health check when 'option httpchk' set

On Sun, Dec 16, 2018 at 12:20 AM Willy Tarreau wrote: > On Sat, Dec 15, 2018 at 11:11:58PM +, Nick Ramirez wrote: > > Thanks! That points me in the right direction. I found that to enable > Layer > > 7 health checks in this case, I would open another port on the web server > > that does not

Re: Setting a unique header per server in a backend

Hi Sachin, On Sat, Dec 15, 2018 at 10:32:21PM +0530, Sachin Shetty wrote: > Hi, > > We have a tricky requirement to set a different header value in the request > based on which server in a backend is picked. > > backend pod0 > ... > server server1 server1:6180 check > server