Re: Adding Serial Number to POST Requests

On Fri, Jul 18, 2014 at 9:12 AM, Neil - HAProxy List maillist-hapr...@iamafreeman.com wrote: Hi Using peers should prevent the reset when restarting? Neil With Willy's solution, yes, it should do the job. Baptiste

question about refresh page

Hi ! I use HA-Proxy version 1.5.1 2014/06/24 Copyright 2000-2014 Willy Tarreau w...@1wt.eu Build options : TARGET = linux2628 CPU = generic CC = gcc CFLAGS = -O2 -g -fno-strict-aliasing OPTIONS = Default settings : maxconn = 2000, bufsize = 16384, maxrewrite = 8192,

Re: HAProxy and SSL through and through

I realize that not everyone may have had those old messages around. I have included my original post below. Also, I've read that using the ssl sessionid is not reliable so I'm looking for an alternative. I was happily using HAProxy, until I received word that we need to also encrypt traffic to

UDP Listener

Hi guys. In my config file there is a string: log 127.0.0.1 local6 info After haproxy restart i receive UDP listener which listens on *:non-priv port. Is there a way to restrict it to some interface/address? 127.0.0.1 for example? Thanks

RE: 100% CPU after upgraded to 1.6dev

Hi Igor, Hi, Had upgrade from 1.5dev 21 to 1.6dev, the CPU usage became insane to 100%, in dev21, it's about 0%. Config file: https://gist.github.com/0c21a67c7be1e7a62a2f Is 1.5.2 stable affected as well? What exact commit are you using in 1.6dev (please post haproxy -vv output)?

Re: 100% CPU after upgraded to 1.6dev

Hi, On 18.07.2014 19:22, Igor wrote: Hi, I use git commit e63a1eb290a1c407453dbcaa16535c85a1904f9e, 1.5.2 same result like git version. When I look at your config, my educated guess would be commit 60d7aeb6e1450995e721d01f48f60b7db4c44e2b. Bests, -Igor On Sat, Jul 19, 2014 at 1:07 AM,

RE: 100% CPU after upgraded to 1.6dev

Hi Igor, hi Thomas, On 18.07.2014 19:22, Igor wrote: Hi, I use git commit e63a1eb290a1c407453dbcaa16535c85a1904f9e, 1.5.2 same result like git version. Ok, can you still post the haproxy -vv output please. Best thing would be if you could git bisect this in the haproxy-1.5 repository. Could

Re: 100% CPU after upgraded to 1.6dev

Hi -vv: ./haproxy -vv HA-Proxy version 1.6-dev0-41 2014/07/12 Copyright 2000-2014 Willy Tarreau w...@1wt.eu Build options : TARGET = linux2628 CPU = native CC = gcc CFLAGS = -O2 -march=native -g -fno-strict-aliasing OPTIONS = USE_LINUX_SPLICE=1 USE_REGPARM=1 USE_OPENSSL=1

RE: [PATCH] Memory corruption building Proxy Protocol V2 header

Hi Willy, hi Dave, Hi Dave, On Thu, Jul 17, 2014 at 02:34:01PM -0400, Dave McCowan wrote: Here is the corrected (and retested) :-) patch. Commit comment: Use temporary trash chunk, instead of global trash chunk in make_proxy_line_v2() to avoid memory overwrite. Thank you, I've just

Strange health check behavior

Hi, I've been reading the documentation and searching the mail list, but one thing is not clear for me. I have nbroc 2, 2 frontends pined to a separate cpu core and 1-1 backend. The bind-process options of these backends are inherited from their parent frontend. Thus, are both processes supposed

RE: 100% CPU after upgraded to 1.6dev

Hi Igor, ./haproxy -vv HA-Proxy version 1.6-dev0-41 2014/07/12 Copyright 2000-2014 Willy Tarreau w...@1wt.eu Build options : TARGET = linux2628 CPU = native CC = gcc CFLAGS = -O2 -march=native -g -fno-strict-aliasing OPTIONS = USE_LINUX_SPLICE=1 USE_REGPARM=1 USE_OPENSSL=1

Découvrez vite les look d'été à moitié prix

Title: Petit Bateau: soldes Cliquez ici pour lire cet e-mail dans votre navigateur.

Re: UDP Listener

Hi Serghei, Hi guys. In my config file there is a string: log 127.0.0.1 local6 info After haproxy restart i receive UDP listener which listens on *:non-priv port. Is there a way to restrict it to some interface/address? 127.0.0.1 for example? It's not currently possible to restrict this

Re: [PATCH] Memory corruption building Proxy Protocol V2 header

Hi Lukas, On Fri, Jul 18, 2014 at 08:30:23PM +0200, Lukas Tribus wrote: FYI when compiling current haproxy-1.5 with openssl, compiler warns: src/connection.c: In function ?make_proxy_line_v2?: src/connection.c:687:5: warning: passing argument 2 of ?ssl_sock_get_remote_common_name? from