Re: http-send-name-header for response?

Hi Cyril, Perfect, that's exactly what I needed, and overlooked in the docs. Thanks! -=Mark On Thu, 09 Feb 2017 12:39:06 -0500, Cyril Bonté wrote: Then use : http-response set-header X-Server %s

Re: HTTP 429 Too Many Requests (tarpit deny_status)

Hi Jarno, On Mon, Feb 06, 2017 at 04:33:01PM +0200, Jarno Huuskonen wrote: > Hi, > > On Mon, Jan 16, Willy Tarreau wrote: > > > The second patch updates http_process_req_common/http_process_tarpit to > > > use deny_status. http_process_tarpit has a switch statement for mapping > > > txn->status

Re: Haproxy reload fails on RHEL 7.2

On Wed, Feb 08, 2017 at 11:39:37PM +, Gunuganti, Uma Maheshwar Rao wrote: > Date: Wed, 8 Feb 2017 23:39:37 + > From: "Gunuganti, Uma Maheshwar Rao" > To: "haproxy@formilux.org" > Subject: Haproxy reload fails on RHEL 7.2 > List-Id:

RE: Haproxy reload fails on RHEL 7.2

Hi Brandon, I don’t see any default haproxy on my VM, also I didn't find file at /usr/lib/systemd/system/haproxy.service. I could see haproxy which I installed 1.7.2 at /etc/init.d/haproxy , attached the same file changing the extension. Thanks, UmaMahesh -Original Message-

RE: Haproxy reload fails on RHEL 7.2

Is there a way I could make 1.7.2 work in RHEL 7.2 ? -Original Message- From: Gunuganti, Uma Maheshwar Rao Sent: Thursday, February 09, 2017 9:35 AM To: 'Brandon Perkins' Cc: haproxy@formilux.org Subject: RE: Haproxy reload fails on RHEL 7.2 Hi Brandon, I don’t

Re: http-send-name-header for response?

Hi Mark, Le 09/02/2017 à 18:16, Mark Staudinger a écrit : Hi Daniel, I provided a stripped-down backend configuration. I am in fact using a persistence cookie, but not for all requests, so I would prefer to avoid that as a means of identifying the particular backend vs. sticking to a

Re: Haproxy reload fails on RHEL 7.2

I think this is your problem, if using systemd please use either the wrapper with this systemd service : https://github.com/horms/haproxy/blob/master/contrib/systemd/haproxy.service.in Or maybe this systemd service : [Unit] Description=HAProxy Load Balancer After=syslog.target network.target

Re: http-send-name-header for response?

Hi! I know this is not exactly what you want, but as your example does not show a persistence cookie, you could use that. See https://cbonte.github.io/haproxy-dconv/1.7/configuration.html#4.2-cookie You could also

http-send-name-header for response?

Hi Folks, Given a setup where I have a backend like so: backend production balance roundrobin hash-type consistent http-check expect status 200 option httpchk GET /\ HTTP/1.1\r\nHost:\ myhost.net\r\nUser-agent:\ healthcheck\r\nConnection:\ close server

Re: http-send-name-header for response?

Hi Daniel, I provided a stripped-down backend configuration. I am in fact using a persistence cookie, but not for all requests, so I would prefer to avoid that as a means of identifying the particular backend vs. sticking to a particular backend server - especially as the cookie does need

Re: Dynamically manage server SSL certificates?

Hi, > Le 7 févr. 2017 à 16:47, Cedric Maion a écrit : > > Hi, > > I'm thinking about using HAProxy to terminate SSL connections for > thousands of domains on a single frontend (using SNI). > I use haproxy for that with live restarts without (seen) the drawbacks you

Re: [PATCH] BUILD: ssl: fix to build (again) with boringssl

Thank you, did the trick. Config haproxy backend server to use SSL like "server s1 s1.local:1000 ssl" will cause segment fault. boringssl/crypto/digest/digest.c:98: EVP_MD_CTX_cleanup: Assertion `ctx->pctx == ((void *)0) || ctx->pctx_ops != ((void *)0)' failed. Aborted On Tue, Feb 7, 2017 at