Re: Restrict HAProxy stats page to a specific IP

2017-06-30 Thread Jarno Huuskonen
Hi, On Fri, Jun 30, Kaushal Shriyan wrote: > Is there a way to restrict HAProxy stats page to a specific IP? > > For example i want to restrict *http://IP:1936/haproxy-stats > * to my office address only Can you try something like this: listen stats_frontend

Re: Restrict HAProxy stats page to a specific IP

2017-06-30 Thread Kaushal Shriyan
On Fri, Jun 30, 2017 at 12:16 PM, Jarno Huuskonen wrote: > Hi, > > On Fri, Jun 30, Kaushal Shriyan wrote: > > Is there a way to restrict HAProxy stats page to a specific IP? > > > > For example i want to restrict *http://IP:1936/haproxy-stats > >

Re: Seeing server termination_state SD after updating from 1.6.11 to 1.7.5

2017-06-30 Thread Christopher Faulet
Le 29/06/2017 à 14:52, Brian Loss a écrit : On Sat, Jun 03, 2017 at 00:19:19 +, Willy Tarreau wrote: On Fri, Jun 02, 2017 at 06:17:38PM +, Bernard McCormack wrote: > I've done some more testing. After changing the frontend ngnix to use ''' > proxy_http_version 1.1''' > The errors

Re: Logging SSL pre-master-key

2017-06-30 Thread Emmanuel Hocdet
Hi Willy, Patrick > Le 30 juin 2017 à 07:00, Willy Tarreau a écrit : > > Hi Patrick, sorry for the delay :-/ > > On Mon, Jun 19, 2017 at 01:54:36PM -0400, Patrick Hemmer wrote: >> Well my argument for keeping the name starting with `ssl_fc_session_` is >> that there is also

Proposal: modify stat socket command feedback

2017-06-30 Thread Andjelko Iharos
Hi all, I'd like to propose for discussion an improvement to the feedback delivered by HAProxy over the stats socket. Currently the feedback of stats socket commands is inconsistent and it can be difficult for external tools issuing socket commands to discern whether the command was successful

Re: Update host for http health check

2017-06-30 Thread Georg Faerber
Hi Jonathan, On 17-06-13 17:04:22, Jonathan Quinn wrote: > I'm trying to implement a health check within HAProxy but update the > host depending on the backend server the request is sent to: I'm curious: Did you implement anything which would be worth to share? Cheers, Georg signature.asc

Re: How can we start haproxy in Linux

2017-06-30 Thread Andrew Smalley
Sabeer The command will kill haproxy by pid number kill $(cat /var/run/haproxy.pid) However a more basic understanding of haproxy will help https://www.haproxy.com/doc/hapee/1.5/administration/init.html Andrew Smalley Loadbalancer.org Ltd. www.loadbalancer.org

Re: 2x filter + keep-alive regressions (1.7 affected)

2017-06-30 Thread Willy Tarreau
Hi Lukas! On Fri, Jun 30, 2017 at 10:09:56PM +0200, Lukas Tribus wrote: > Hello Christopher, William, Willy, et all! > > > Matt McDonagh reported a regression on discourse [1] in 1.7.6, that > causes haproxy to ignore "timeout http-keep-alive" when going through > filters (aka compression is

2x filter + keep-alive regressions (1.7 affected)

2017-06-30 Thread Lukas Tribus
Hello Christopher, William, Willy, et all! Matt McDonagh reported a regression on discourse [1] in 1.7.6, that causes haproxy to ignore "timeout http-keep-alive" when going through filters (aka compression is enabled) and also causes logging to be delayed. Because timeouts are ignored and wrong

Re: Proposal: modify stat socket command feedback

2017-06-30 Thread Dennis Jacobfeuerborn
On 30.06.2017 13:43, Andjelko Iharos wrote: > Hi all, > > I'd like to propose for discussion an improvement to the feedback > delivered by HAProxy over the stats socket. > > Currently the feedback of stats socket commands is inconsistent and it > can be difficult for external tools issuing

Re: Logging SSL pre-master-key

2017-06-30 Thread Patrick Hemmer
On 2017/6/30 01:00, Willy Tarreau wrote: > Hi Patrick, sorry for the delay :-/ > > On Mon, Jun 19, 2017 at 01:54:36PM -0400, Patrick Hemmer wrote: >> Well my argument for keeping the name starting with `ssl_fc_session_` is >> that there is also `ssl_fc_session_id`. These 2 fetches pull their >>

Re: Logging SSL pre-master-key

2017-06-30 Thread Willy Tarreau
Hi Patrick, On Fri, Jun 30, 2017 at 10:28:11AM -0400, Patrick Hemmer wrote: > > The issue I'm having is that there's no notification > > that this will not work. Using #ifdef ensures that what is not supported > > will > > report an error. Then the user looks at the keyword in the doc and reads