Re: Require info on ACL for rate limiting on per URL basis.

2019-02-21 Thread Jarno Huuskonen
Hi, On Thu, Feb 21, Badari Prasad wrote: > But by replacing 'src' with 'path', rate-limiting did not work. My current > config after the change is : > > backend st_src_as2_monte > stick-table type string len 64 size 1m expire 1s store http_req_rate(1s) (for testing it helps to use longer

Re: Idea for the Wiki

2019-02-21 Thread Willy Tarreau
On Fri, Feb 22, 2019 at 01:54:00AM +0100, Tim Düsterhus wrote: > I suggest to create new pages using the web interface only to make sure > it can handle it. Editing can be done using git. I agree. I'm seeing antoher benefit to this, which is that it will guarantee that we only use simple things

Re: Idea for the Wiki

2019-02-21 Thread Tim Düsterhus
Baptiste, Am 20.02.19 um 07:44 schrieb Baptiste: > I just cloned the repo :) > How should we organize directories and pages? > IE for TLS offloading: > /common/acceleration/tls_offloading.md ? > I think it's quite important to agree on it now, because the folders will > be part of the URL

Re: error in haproxy 1.9 using txn.req:send in lua

2019-02-21 Thread Thierry Fournier
Hi, You can use something like that: --> receive request from client --> frontend a --> use-service lua.xxx --> [forward data using core.tcp(127.0.0.1:) --> frontend (bind 127.0.0.1:) --> [send request to your server] --> [receive response] --> [read response in

Re: Require info on ACL for rate limiting on per URL basis.

2019-02-21 Thread Badari Prasad
Hi, Thank you for response, I would want to have rate-limiting on url no matter what src ip is. So one difference I noticed is : http-request track-sc1 src table st_src_as2_monte unless monte_as2_exceeds_limit >From your example I see: http-request track-sc0 path table test_be But by

Re: RTMP and Seamless Reload

2019-02-21 Thread Aleksandar Lazic
Hi Erlangga. Am 20.02.2019 um 07:24 schrieb Erlangga Pradipta Suryanto: > Hi Aleksandar, > > Very sorry for the late reply. I was out of the office. >> Ah OBS (=Open Broadcaster Software ?) something like this? > Yes, the open broadcaster software, that's the tool that we use in our >

Re: %[] in use-server directives

2019-02-21 Thread Joe K
Ah, I see. Tried it, but it seems it's not the only thing that causes the segfault. On Thu, Feb 21, 2019 at 8:31 AM Willy Tarreau wrote: > Hi Joe, > > On Thu, Feb 21, 2019 at 08:23:29AM +, Joe K wrote: > > Hello everybody again ... > > > > So here's what I have right now, just from

Re: %[] in use-server directives

2019-02-21 Thread Willy Tarreau
Hi Joe, On Thu, Feb 21, 2019 at 08:23:29AM +, Joe K wrote: > Hello everybody again ... > > So here's what I have right now, just from copy-pasting and slightly > editing 702d44f. > > The config check passes, but haproxy crashes with segmentation fault after > the first request with an

Re: Tune HAProxy in front of a large k8s cluster

2019-02-21 Thread Baptiste
On Wed, Feb 20, 2019 at 3:14 PM Joao Morais wrote: > > > > Em 20 de fev de 2019, à(s) 03:30, Baptiste escreveu: > > > > Hi Joao, > > > > I do have a question for you about your ingress controller design and > the "chained" frontends, summarized below: > > * The first frontend is on tcp mode

Re: %[] in use-server directives

2019-02-21 Thread Joe K
Hello everybody again ... So here's what I have right now, just from copy-pasting and slightly editing 702d44f. The config check passes, but haproxy crashes with segmentation fault after the first request with an enabled server. On Tue, Feb 19, 2019 at 9:24 AM Willy Tarreau wrote: > On Tue,