Re: acl regex

Hi Cyril, On Tue, Nov 24, 2015 at 10:58:47PM +0100, Cyril Bonté wrote: > Currently, haproxy won't match an url parameter if its value is empty. I > tend to think it should : an empty value is different from not providing > the parameter at all. > > The function "find_next_url_param()" should un

Re: acl regex

Hi all, I should be able to test this in our production setup a few days after I can have an rpm ready with the patch we are running on rhel 6.x Merci Cyril --- Guillaume Bourque, B.Sc., Le 2015-11-24 à 16:58, Cyril Bonté a écrit : > Hi all, > > I revive this thread. > > Le 12/11/2015 09

Re: acl regex

Hi all, I revive this thread. Le 12/11/2015 09:59, Igor Cicimov a écrit : On Thu, Nov 12, 2015 at 6:44 PM, Guillaume Bourque mailto:guillaume.bour...@logisoftech.com>> wrote: Hi, thanks for the suggestion but it did not work for me. I tried acl fr_top url

ORLANDO , la ville du futur , the city of the future

ORLANDO , la ville du futur , the city of the future   Placement garanti 6 ans  

Re: ssl parameters ignored

Hi Nenad, On 2015-11-24 16:15, Nenad Merdanovic wrote: Can you post a minimal configuration (or full) which reproduces this? Yes, here it is: global log /dev/loglocal0 log /dev/loglocal1 notice chroot /var/lib/haproxy stats socket /run/haproxy/admin.soc

Re: ssl parameters ignored

Hello, On 11/24/2015 1:47 PM, Sander Klein wrote: > On 2015-11-23 22:36, Lukas Tribus wrote: >> Can you elaborate what kind of OS we are talking about, and where the >> openssl lib comes from (is it just a openssl-dev package from the >> repository, or a custom build? static or shared?) > > It is

Re: Re: CPU 100% when waiting for the client timeout

Ok, Thanks :-) -- Best Regards BaiYang baiy...@gmail.com http://baiy.cn < END OF EMAIL > From: Willy Tarreau Date: 2015-11-24 23:05 To: baiyang CC: Lukas Tribus; haproxy Subject: Re: Re: CPU 100% when waiting for the client timeout On Tue, Nov 24, 2015 at 03:06:15PM +080

Re: Re: CPU 100% when waiting for the client timeout

Hi Willy I've found generally it is very peaceful with the first 24 hours after a reboot. And usually one reproducing in the next day. And more frequently (2-3 reproducing) at the third day. May be it's a tip? :-) -- Best Regards BaiYang baiy...@gmail.com http://baiy.cn < END

Re: Re: CPU 100% when waiting for the client timeout

On Tue, Nov 24, 2015 at 03:06:15PM +0800, baiyang wrote: > I caught both strace log and show sess all output this time: > http://baiy.cn/tmp/log-1124.rar ... and it paid quickly : 0x2890810: [24/Nov/2015:14:38:54.760319] id=708867 proto=tcpv4 source=182.148.111.97:6085 flags=0x24348e, conn_re

Re: Re: CPU 100% when waiting for the client timeout

Hi Baiyang, On Tue, Nov 24, 2015 at 03:06:15PM +0800, baiyang wrote: > I caught both strace log and show sess all output this time: > http://baiy.cn/tmp/log-1124.rar Just downloaded it, thanks! Willy

RE: ssl parameters ignored

Hi, On 2015-11-23 22:36, Lukas Tribus wrote: Are you sure that the executable was cleanly build (first "make clean", only then "make ...")? I don't know. I got pre made packages from "http://haproxy.debian.net jessie-backports-1.6 main" maintained by Vincent Bernat if I'm correct. Can you

Re: Could we reduce spam in the list?

Yeah On 23/11/2015 21:20, Willy Tarreau wrote: On Mon, Nov 23, 2015 at 03:20:06PM +0100, Vincent Gallissot wrote: This is obviously a spam and Barracuda let it go. Don't you use other headers to help yourself detect spams ? Cause this is really annoying on this mailing list. What is even more

Re: Owncloud through Haproxy makes upload not possible

I'm not sure why, but after doing haproxy -vv I now get kevent() in truss output. I'm attaching another truss output. While browsing the logs I've notices that besides the usual 200 output, when uploading was finished (unsuccessfully) I got the following 504 code: Nov 24 11:03:13 anongoth haproxy[7

unsubscribe