stick-table functionality broken after upgrade

Hi, We recently upgraded from a 18 month-old pre-release version of haproxy 1.5 to haproxy 1.5.9, and our sticky session functionality has broken. Specifically, our application needs to direct groups of users to specific servers based on certain user characteristics. The way this works is that

RE: Error 400 (BADREQ) on some requests -

> Le 22/12/2014 19:00, Lukas Tribus a écrit : >>> OK, got it. >>> >>> What should I do with HAProxy to handle with them? (option >>> accept-invalid-http-request is set already) >> >> You can't. HAproxy will not support those URI's. >> >> accept-invalid-http-request allows a limited set of forbidden

Re: Error 400 (BADREQ) on some requests -

Hi Juriy and Lukas, while scrolling into the code, I hit a part of code which reminded me this thread. Le 22/12/2014 19:00, Lukas Tribus a écrit : OK, got it. What should I do with HAProxy to handle with them? (option accept-invalid-http-request is set already) You can't. HAproxy will not

Re: using environment variable in headers

Hi Pavlos, Le 06/01/2015 20:17, Pavlos Parissis a écrit : Hi, According to the docs I can have the following snippet http-request add-header Nodename %[env(HOSTNAME)] to set the hostname as the value on a header. But, it doesn't work. I network trace and Nginx logs show no value. Please ens

using environment variable in headers

Hi, According to the docs I can have the following snippet http-request add-header Nodename %[env(HOSTNAME)] to set the hostname as the value on a header. But, it doesn't work. I network trace and Nginx logs show no value. While the following works. http-request add-header Nodename %H I am usi

Capturing 'dynamic' request headers

Hi, How do I do: acl REQUEST_TOO_BIG hdr_val(content-length) gt 2 http-request add-header X-Haproxy-TARPIT %[req.fhdr(X-Haproxy-TARPIT,-1)]request-too-big, if METH_POST REQUEST_TOO_BIG and then later capture request header X-Haproxy-TARPIT len 256 So that it's added to the log? I'm running

Upcoming OpenSSL API changes and haproxy incompatibilities

Hi folks, there are some API changes (most structures will became opaque) in OpenSSL that will break the build with haproxy. It appears that we will see a 1.1.0 release with those changes by the end of 2015 [1]. Some of this can be reproduced by linking haproxy against current openssl ma

HAProxy 1.5.10 git tag

Could you possibly tag the 1.5.10 release in git? Our CI/CD process relies on tags to build new releases :-) -- Erik Weber