Re: 'acl' and 'use_backend' in defaults section?

unfortunately, for now you'll have to repeat the acl in each frontend :) Baptiste On Tue, Apr 7, 2015 at 9:14 PM, Florin Andrei flo...@andrei.myip.org wrote: I have a few ACLs that are identical for several frontends. I tried to define the ACLs in the defaults section, but I got an error

[SPAM] MAIL UPGRADE

Hi haproxy@formilux.org I'd like to connect with you on LinkedIn.am a new buyer Yusuf Alim Manager at KAHN TRADING CO. LLC | DUBAI popular

Re: AW: forward client disconnects in http mode

On 09/04/2015 02:52 μμ, Dieter van Zeder wrote: ‎Here's the the stripped-down configuration. Http-server-close is required in order to use leastconn. The frontend actually contains various acl rules, thus mode http. I had a look at the doc and it isn't mentioned that http-server-close is

Re: How to profile stats web page users

I think you want ACL-driven stats scope statements, which don't exist to the best of my knowledge. In your case, rather than open a bunch of different ports, I'd give people different FQDNs to hit, and point a wildcard DNS record at a single port 80. (Well, a :443 with TLS, if I were doing it,

How to profile stats web page users

Hi all. I currently give access to the stats page using a simple profiling by groups . amministratori that have admin access to everything . readonly that have no admin acces to everything All users see the full set of listen, frontend and backend sections. userlist stats-auth

AW: forward client disconnects in http mode

‎Here's the the stripped-down configuration. Http-server-close is required in order to use leastconn. The frontend actually contains various acl rules, thus mode http. Thank you!  Dieter ‎defaults         option abortonclose         balance leastconn   backend apache         mode http          

Re: [PATCH 1/2] MEDIUM: Only report drain state in stats if server has SRV_ADMF_DRAIN set

Hi Simon! On Thu, Apr 09, 2015 at 03:47:13PM +0900, Simon Horman wrote: There are some similarities between a weight of zero and the administratively set drain state: both allow existing connections to continue while not accepting any new ones. However, when reporting a server state

Re: [PATCH] Add a new log format variable %p that spits out the sanitized request path

Hi Willy - Apologies if this comes through multiple times; I'm having some mail difficulties. On Tue, Apr 7, 2015 at 7:11 PM, Willy Tarreau w...@1wt.eu wrote: Just a question, did you find any benefit in doing it with a new tag compared to %[path] ? It may just be a matter of convenience, I'm

possible header capture corruption when timeout queue

Greetings, I hope the rewrite from C-Lua is going well... I'm looking to trace down a weird scenario that might be a bug. We're running: 1.5.2. Our backend is configured w/ a 500ms timeout queue and we consistent hash on uri for load balancing. For requests logged as termination 'SQ' that

Re: Haproxy session time out

Hi Cyrill, Thanks for the update. Please find the attached configuration. Also please respond to below my queries. In our configuration client time out set as 50sec. What will be the result if the user remain inactive more than 50sec? lets say a user hits goes to App1 server. if user remains

Re: [PATCH 1/2] MEDIUM: Only report drain state in stats if server has SRV_ADMF_DRAIN set

Willy / Simon, I think I've got a bit confused myself - I've just installed the patches and tested and it fixes the issues we seeing with HAProxy getting stuck in DRAIN mode when the agent temporarily responds with 0% idle. i.e. when the load on the server decreases HAProxy should automatically

[PATCH 0/2] Minor enhancements to drain state

Hi, these two patches suggest the following enhancements to Drain. The second patch has context dependencies on the first one. 1. Only report drain state in stats if server has SRV_ADMF_DRAIN set The motivation is to consistently differentiate between between state=UP,weight=0 and

[PATCH 2/2] MEDIUM: Differentiate between DRAIN and DRAIN (agent)

Differentiate between DRAIN and DRAIN (agent) when reporting stats. This is consistent with the distinction made between DOWN and DOWN (agent). Signed-off-by: Simon Horman ho...@verge.net.au --- src/dumpstats.c | 21 ++--- 1 file changed, 14 insertions(+), 7 deletions(-) diff

[PATCH 1/2] MEDIUM: Only report drain state in stats if server has SRV_ADMF_DRAIN set

There are some similarities between a weight of zero and the administratively set drain state: both allow existing connections to continue while not accepting any new ones. However, when reporting a server state generally a distinction is made between state=UP,weight=0 and state=DRAIN,weight=*.

Re: cohaproxy

Hello That's an error from tomcat? Up the nofiles in etc security limits is normal way to do that Neil On 9 Apr 2015 18:50, ballu balram ballubalram...@gmail.com wrote: Hi, After installing haproxy in ubuntu i get error ;- *29-Mar-2015 06:47:43.963 SEVERE [http-nio-9191-Acceptor-0]

Re: AW: forward client disconnects in http mode

On 09/04/2015 02:11 μμ, Dieter van Zeder wrote: It's not about idle connections, it's about connections closed by the client before the server fully sent the response. I have an apache module which can detect client disconnects and then stops processing.‎ Having haproxy before those

Re: How to profile stats web page users

Have you looked at stats scope? https://cbonte.github.io/haproxy-dconv/configuration-1.5.html#stats%20scope Jonathan

Re: limiting conn-curs per-ip using x-forwarded-for

Hi Klavs, Please give a try to the configuration below: frontend nocache mode http .. option httplog option accept-invalid-http-request stick-table type ip size 100k expire 30s store conn_cur tcp-request inspect-delay 5s tcp-request content accept if HTTP tcp-request content

Re: [PATCH 1/2] MEDIUM: Only report drain state in stats if server has SRV_ADMF_DRAIN set

Hi Malcolm, On Thu, Apr 09, 2015 at 02:31:16PM +0100, Malcolm Turnbull wrote: Willy / Simon, I think I've got a bit confused myself - I've just installed the patches and tested and it fixes the issues we seeing with HAProxy getting stuck in DRAIN mode when the agent temporarily responds

Re: forward client disconnects in http mode

On 09/04/2015 12:52 μμ, Dieter van Zeder wrote: Hi there, is it possible to forward packets indicating a client disconnect, with haproxy running in http mode? The webserver is able to cancel long running requests, but the disconnect cannot be detected at the backend. I don't quite

Re: stats uri doesn't inherit from defaults sections

On Thu, Apr 9, 2015 at 7:03 AM, Jonathan Matthews cont...@jpluscplusm.com wrote: Hi all - A bit of lunchtime playing around today has exposed the fact that a stats uri in a defaults section has no effect on backends to which the defaults section /should/ apply. Stats-serving backends only

forward client disconnects in http mode

Hi there, is it possible to forward packets indicating a client disconnect, with haproxy running in http mode? The webserver is able to cancel long running requests, but the disconnect cannot be detected at the backend.Kind regardsDieter

Re: AW: forward client disconnects in http mode

Haproxy closes the connection with an RST. Baptiste Le 9 avr. 2015 16:54, Pavlos Parissis pavlos.paris...@gmail.com a écrit : On 09/04/2015 02:52 μμ, Dieter van Zeder wrote: ‎Here's the the stripped-down configuration. Http-server-close is required in order to use leastconn. The frontend