Re: Few problems seen in haproxy? (threads, connections).

2018-10-05 Thread Willy Tarreau
Hi Krishna, On Fri, Oct 05, 2018 at 02:25:13PM +0530, Krishna Kumar (Engineering) wrote: > Sorry for repeating once again, but this is my last unsolicited > mail on this topic. Any directions for what to look out for? Sorry, but I didn't even have the time to read your mail over the last two days

Re: lua haproxy-auth-request - round 2

2018-10-05 Thread Computerisms Corporation
Hi Tim, Thanks for the response, and apologies for the delay. Popularity is advertised as a good thing, but I have my doubts. Regardless, I am back on track with this project for the moment. While I don't have any idea from the top of my head your configuration surely would be helpful. rig

Re: Combine different ACLs under same name

2018-10-05 Thread Ricardo Fraile
El vie, 05-10-2018 a las 11:38 +0200, Jerome Magnin escribió: > Hello, > > On Fri, Oct 05, 2018 at 10:46:20AM +0200, Ricardo Fraile wrote: > > Hello, > > > > > > I have tested that some types of acls can't be combined, as example: > > > > Server 192.138.1.1, acl with combined rules: > > > >

Re: Combine different ACLs under same name

2018-10-05 Thread Jerome Magnin
Hello, On Fri, Oct 05, 2018 at 10:46:20AM +0200, Ricardo Fraile wrote: > Hello, > > > I have tested that some types of acls can't be combined, as example: > > Server 192.138.1.1, acl with combined rules: > > acl rule1 hdr_dom(host) -i test.com > acl rule1 src 192.168.1.2/24 >

Re: Few problems seen in haproxy? (threads, connections).

2018-10-05 Thread Krishna Kumar (Engineering)
Sorry for repeating once again, but this is my last unsolicited mail on this topic. Any directions for what to look out for? Thanks, - Krishna On Thu, Oct 4, 2018 at 8:42 AM Krishna Kumar (Engineering) < krishna...@flipkart.com> wrote: > Re-sending in case this mail was missed. To summarise the

Combine different ACLs under same name

2018-10-05 Thread Ricardo Fraile
Hello, I have tested that some types of acls can't be combined, as example: Server 192.138.1.1, acl with combined rules: acl rule1 hdr_dom(host) -i test.com acl rule1 src 192.168.1.2/24 redirect prefix https://yes.com code 301 if rule1 redirect prefix https://no

Compression disabling on chunked response

2018-10-05 Thread Sachin Shetty
Hi, I see this in the documentation: Compression is disabled when: * ... * response header "Transfer-Encoding" contains "chunked" (Temporary Workaround) * Is this still accurate? I have tested a lot of responses from Server with compression enabled in backend and server