haproxy resolvers "nameserver: can't connect socket" (on FreeBSD)

Hi guys, Hoping someone can shed some light on what i might be doing wrong? Or is there something in FreeBSD that might be causing the trouble with the new resolvers options? Thanks in advance. PiBa-NL haproxy -f /var/haproxy.cfg -d [ALERT] 248/222758 (22942) : SSLv3 support requested but

Re: DNS: defaulting resolve-prefer to ipv6 can lead to unexpected results

Le 6 sept. 2015 18:53, "Conrad Hoffmann" a écrit : > > Hi, > > I ran into the following problem: I have a server specified by hostname, > using the new DNS feature. I initially did not specify the "resolve-prefer" > parameter. The initial lookup of the server succeeded and

Re: Migration from nginx

On Sat, 5 Sep 2015 18:13:57 +0300 Vladimir Mihailenco wrote: > Thanks for advice. It turns out that Go silently (without any reply and log > message) closes the connection when it can't fully read request headers. > Which is kinda strange, because I thought that

Re: Lua outbound Sockets in 1.6-dev4

Thank you, Will had just applied the patch on the current development branch. Thierry On Sat, 5 Sep 2015 15:28:10 -0400 Michael Ezzell wrote: > I can confirm, the patch appears to work correctly. Thank you for the fix. > . > > On Fri, Sep 4, 2015 at 1:08 PM, Thierry

DNS: defaulting resolve-prefer to ipv6 can lead to unexpected results

Hi, I ran into the following problem: I have a server specified by hostname, using the new DNS feature. I initially did not specify the "resolve-prefer" parameter. The initial lookup of the server succeeded and produced an IPv4 address. Unfortunately, that address was then never updated because