Re: Change backend between a time frame

On Sat, Nov 18, 2017 at 03:02:07PM +1100, Igor Cicimov wrote: > On Sat, Nov 18, 2017 at 2:35 AM, GARET Julien > wrote: > > > Hello, > > > > > > > > I have a use case here where we want to be able to modify the backend > > between 8 pm et and 8 am, everyday. I was guessing that it would have > > s

Re: [BUG] haproxy 1.8-last/master-worker/peers

Hi Manu, On Fri, Nov 17, 2017 at 05:14:11PM +0100, Emmanuel Hocdet wrote: > In master-worker mode with peers, old worker never died after a reload (kill > -USR2). > > Tested without traffic, with/without threads. > Without peers, no problems. Thanks for the report. I'm currently working on an i

Re: question about fc_rcvd_proxy

Hi Clément, On Sat, Nov 18, 2017 at 02:04:20AM +, Clément Guillaume wrote: > Hello, > > I'm trying to use fc_rcvd_proxy to detect if Proxy Protocol should be used > (tcp-request connection expect-proxy layer4), but it always returns false. > An AWS ELB is adding the Proxy Protocol header. I p

[PATCH] MEDIUM: mworker: Add systemd `Type=notify` support

This patch adds support for `Type=notify` to the systemd unit. Supporting `Type=notify` improves both starting as well as reloading of the unit, because systemd will be let known when the action completed. See this quote from `systemd.service(5)`: > Note however that reloading a daemon by sending

Add systemd `Type=notify` support

This patch has been verified using systemd 229 on Ubuntu 16.04. I've tested the following cases: - haproxy properly sends READY=1 to systemd (because otherwise the unit would not have been marked as running in systemd). - haproxy properly sends RELOADING=1 to systemd (by removing the READY=1 I

Re: [PATCH] MEDIUM: mworker: Add systemd `Type=notify` support

Hi Tim. -- Originalnachricht -- Von: "Tim Düsterhus" An: haproxy@formilux.org Cc: wlallem...@haproxy.com; "Tim Düsterhus" Gesendet: 18.11.2017 20:02:23 Betreff: [PATCH] MEDIUM: mworker: Add systemd `Type=notify` support This patch adds support for `Type=notify` to the systemd unit. S

[PATCH v2 1/1] MEDIUM: mworker: Add systemd `Type=notify` support

From: Tim Duesterhus This patch adds support for `Type=notify` to the systemd unit. Supporting `Type=notify` improves both starting as well as reloading of the unit, because systemd will be let known when the action completed. See this quote from `systemd.service(5)`: > Note however that reload

[PATCH v2 0/1] Add systemd `Type=notify` support

Aleksandar, I added `USE_SYSTEMD` to the `BUILD_OPTIONS` and moved the whole block down below the `USE_WURFL` block to match the ordering in the comment at the top of the file. I also noticed a blank line I added by accident. I removed that one in this new patch also. Thanks Tim Düsterhus Tim D

Re: [PATCH v2 1/1] MEDIUM: mworker: Add systemd `Type=notify` support

Hi. -- Originalnachricht -- Von: "Tim Düsterhus" An: haproxy@formilux.org Cc: "Tim Duesterhus" ; wlallem...@haproxy.com; a...@none.at Gesendet: 19.11.2017 03:10:21 Betreff: [PATCH v2 1/1] MEDIUM: mworker: Add systemd `Type=notify` support From: Tim Duesterhus This patch adds supp

Is it possible to transfer client ip (src) from ssl:443 to https:8443?

client access ssl:443. https:8443 as backend of ssl:443. Is it possible to transfer client ip (src) from ssl:443 to https:8443? Or transfer a true/false variable, so https:8443 can decide accept or deny? Example: frontend https bind *:8443 ssl crt /etc/haproxy/certs/default backend https-b

Re: [PATCH v2 1/1] MEDIUM: mworker: Add systemd `Type=notify` support

Hi Aleks, On Sun, Nov 19, 2017 at 02:32:53AM +, Aleksandar Lazic wrote: > Maybe my client is crap but I see the patches inline. > Please can you be so kind and create a patch file which is attached to the > mail. Well, inline patches are not a problem, they apply well (it's even the original

Re: HAProxy SMTP Rate limiting

Hello, On Sun, Nov 12, 2017 at 09:19:33AM -0500, SAFENTRIX Administrator wrote: > We are using HAProxy v 1.6.4 for SMTP load balancing (in transparent mode) > and it works fine. > > Now we want to block connections from IP addresses that abuse the Email > server. > > One way to identify thi

Re: HAProxy LB causes server to poll for request data for a long time

Hi, On Thu, Nov 16, 2017 at 09:15:02PM +0500, ??? wrote: > Try > > proxy_buffering off; > proxy_request_buffering off; > > in nginx Good point, it's indeed possible that some slow clients are keeping application connections opened and that the default buffering in nginx hides it. It's

Re: HAProxy LB causes server to poll for request data for a long time

On Sun, Nov 19, 2017 at 07:45:59AM +0100, Willy Tarreau wrote: > On Thu, Nov 16, 2017 at 09:15:02PM +0500, ??? wrote: > > Try > > > > proxy_buffering off; > > proxy_request_buffering off; > > > > in nginx > > Good point, it's indeed possible that some slow clients are keeping > applicat