Re: resolvers - resolv.conf fallback

Hello Baptiste, > - (for Lukas) what do you think is better, a configuration option to trigger > parsing of resolv.conf or as proposed, if no nameserver are found, we use > resolv.conf as a failback? I don't think we need a config knob for this; currently we don't do anything when no

Re: Rejected connections not getting counted in stats

Hi Errikos, On 26/03/2018 13:03, Errikos Koen wrote: > Hello, > > I have a frontend whitelisted by IP with the following rules: > > acl whitelist src -f /etc/haproxy/whitelist.lst > tcp-request connection reject unless whitelist > > and while documentation >

Re: DNS resolver and mixed case responses

Dale, Am 03.04.2018 um 16:17 schrieb Dale Smith: I'm trying to understand what system is at fault here; the DNS server for not responding with the same case as the query, or HAProxy which should be performing a case insensitive match. This is left unspecified in the standards, but on the

Re: [PATCH] BUG/MINOR: email-alert: Set the mailer port during alert initialization

On Tue, Mar 27, 2018 at 04:04:40PM +0200, Christopher Faulet wrote: > Hi, > > This patch fixes an issue about email alerts reported by Johan. It must be > backported in 1.8. > > Johan, could you confirm it fixes the bug ? Out of response I've merged it now, thank you Christopher. Willy

No enabled listener found and reloads triggered an inconsistent state.

Hi there, We had an issue recently, using 1.8.5. For some reason we ended up entering in the "No enabled listener found" state (I guess the config file was incomplete, being written at that time, something like that). Here are the logs: Apr 03 17:51:49 hostname systemd[1]: Reloaded HAProxy

Re: DNS resolver and mixed case responses

On Tue, 3 Apr 2018 at 17:35 Baptiste wrote: > > Hi Dale, > > Thanks for the report! > Please share your patch here and I'll have a look, so we could merge it. > > Baptiste > Hi Baptiste, I've attached a patch file for haproxy-1.7 that performs the case insensitive match