❦ 3 février 2016 00:11 GMT, David Birdsong :
> I'm not using consul but am using haproxy in a docker container
> and reloading when backend hosts change registrations. I haven't
> seen this issue. I run using haproxy-systemd-wrapper and HUP that
>
On Wed, Feb 3, 2016 at 3:05 AM Vincent Bernat wrote:
> ❦ 3 février 2016 00:11 GMT, David Birdsong :
>
> > I'm not using consul but am using haproxy in a docker container
> > and reloading when backend hosts change registrations. I haven't
> >
Hi,
I have a question about cookie prefix mode. I use configuration like this:
backend b1
balance roundrobin
cookie JSESSIONID prefix
server s1 192.168.122.1:8080 cookie c1
Now the docs
https://cbonte.github.io/haproxy-dconv/configuration-1.6.html#4-cookie for
prefix say:
Since all
Hi David,
On Tue, Feb 02, 2016 at 11:56:25PM +, David Birdsong wrote:
> Has nobody else run into this w/ consul? Given the plethora of tools around
> consul and haproxy and templating, I know others are using reloads to keep
> backend current, but the old haproxy PIDs stick around listening
On Thu, Jan 28, 2016 at 12:25:05PM +0100, Aleksandar Lazic wrote:
>
>
> Am 28-01-2016 12:01, schrieb Jonathan Leroy - Inikup:
> >2016-01-28 11:47 GMT+01:00 Lukas Tribus :
> >>Doesn't:
> >>http-request set-src hdr(CF-Connecting-IP)
> >>
> >>in combination with a standard
Hello Dmitry,
On Thu, Jan 28, 2016 at 05:31:58PM +0300, Dmitry Sivachenko wrote:
> Hello,
>
> I have an option http-ignore-probes in defaults section.
> When I declare frontend in "tcp" mode, I get the following warning:
>
> [WARNING] 027/172718 (18281) : config : 'option http-ignore-probes'
On Wed, Feb 03, 2016 at 11:05:03AM +1100, Igor Cicimov wrote:
> Any comments on this? Shouldn't the expiration time get replicated upon
> restart or just the keys? Obviously the entry in the first server stick
> table will expire much sooner than the one on the restarted server meaning
> the first
Hi,
On Sun, Jan 31, 2016 at 09:16:23PM +, Cain wrote:
> Hi,
>
> Sometimes I find i am left with zombie haproxy instances that are *still
> listening* and do *not* have any established connections (netstat told me
> so), even though those particular pids have been told to die.
>
> I.e.
>
>
Hi Lukas,
On Wed, Feb 03, 2016 at 06:09:37PM +0100, Lukas Tribus wrote:
> Micha?? Pasierb reported doc inconsistencies regarding the old default
> HTTP tunnel mode.
>
> This patch fixes a few of those inconsistencies and should be backported
> to both 1.6 and 1.5.
Applied to 1.7-dev, thanks!
> Now I did the same setup with version 1.5 and found out that even
> without "option httpclose" both requests have the cookie prefixed.
>
> My dillema - are the docs inconsistent and this section should be
> removed or am I missing something ?
Docs are inconsistens both 1.5 and 1.6 for this.
❦ 3 février 2016 14:37 GMT, David Birdsong :
> right, thanks, but again, I'm familiar w/ haproxy and graceful
> reloads. I've used lsof -Pnp , and I find that sometimes an old
> haproxy process is still listening for new connections. This is the
> problem I'm trying
Michał Pasierb reported doc inconsistencies regarding the old default
HTTP tunnel mode.
This patch fixes a few of those inconsistencies and should be backported
to both 1.6 and 1.5.
---
doc/configuration.txt | 28
1 file changed, 12 insertions(+), 16 deletions(-)
Hi Willy,
>> This patch fixes a few of those inconsistencies and should be backported
>> to both 1.6 and 1.5.
>
> Applied to 1.7-dev, thanks!
thanks.
A minor cosmetic glitch: seems that something broke non-ascii characters,
I can see it in this commit here and also in Cyril's latest patch,
Hi Lukas,
On Wed, Feb 03, 2016 at 07:47:37PM +0100, Lukas Tribus wrote:
> Hi Willy,
>
>
> >> This patch fixes a few of those inconsistencies and should be backported
> >> to both 1.6 and 1.5.
> >
> > Applied to 1.7-dev, thanks!
>
> thanks.
>
> A minor cosmetic glitch: seems that something
14 matches
Mail list logo