Re: Re: [PATCH] BUG/MINOR: ssl: fix potential memory leak in ssl_sock_load_dh_params()

Hi Rémi, sorry for the slow reply :-( On Sat, Jul 02, 2016 at 04:47:57PM +0200, Remi Gacogne wrote: > Hi Willy, Roberto, Emeric, > > On 06/30/2016 08:12 PM, Willy Tarreau wrote: > > I checked the man page for SSL_CTX_set_tmp_dh() and it does not mention > > anything regarding the need to free

Re: counters for specific http status code

Hi Ruoshan, On Tue, Jul 05, 2016 at 12:28:43PM +0800, Ruoshan Huang wrote: > hi, > I use the hrsp4xx/hrsp5xx a lot to do timeseries metric collecting, > sometimes the these counters lack details. I'm wondering what's the > badside of no collecting all the HTTP status (just an array of

Re: counters for specific http status code

hi, > On Jul 12, 2016, at 12:05 PM, Willy Tarreau wrote: > > Hi Ruoshan, > > On Tue, Jul 05, 2016 at 12:28:43PM +0800, Ruoshan Huang wrote: >> hi, >>I use the hrsp4xx/hrsp5xx a lot to do timeseries metric collecting, >>sometimes the these counters lack details. I'm

Re: [ANNOUNCE] haproxy-1.6.6

❦ 30 juin 2016 20:19 CEST, Willy Tarreau  : >> - BUG/MINOR: ssl: fix potential memory leak in ssl_sock_load_dh_params() > > For those interested, we found a regression with this patch, some of our > processes crash with openssl-1.0.2 and dh-param 1024. Setting dh-param 2048 > is

Re: counters for specific http status code

On Tue, Jul 12, 2016 at 12:29:56PM +0800, Ruoshan Huang wrote: > Indeed I only care about 20 status code or so, like 400, 401, 403 (I have > been bitten many times by treating those codes as 404 :( ), and 50x also > helps a lot in our alerting system as a first method for diagnosing abnormal >

Re: [ANNOUNCE] haproxy-1.6.6

Hi Vincent, On Tue, Jul 12, 2016 at 06:34:00AM +0200, Vincent Bernat wrote: > ??? 30 juin 2016 20:19 CEST, Willy Tarreau  : > > >> - BUG/MINOR: ssl: fix potential memory leak in ssl_sock_load_dh_params() > > > > For those interested, we found a regression with this patch, some of

Re: counters for specific http status code

> On Jul 12, 2016, at 12:42 PM, Willy Tarreau wrote: > > Please take a look at how track-sc are added to http-request, look for > "ACT_ACTION_TRK_SC0" in proto_http.c, you'll find your way through it, > and see if you can duplicate this to the response. There should be a few >

Re: [ANNOUNCE] haproxy-1.6.6

❦ 12 juillet 2016 06:44 CEST, Willy Tarreau  : >> If you say you won't have time before >> end of july, I can do an upload now. If you say you will do it on next >> week-end, I will happily wait and congratulate myself for not uploading >> too soon. > > Let's say that if on

Enfin de la telephonie illimitee pro

243092513.png Description: Binary data <> 937400192.png Description: Binary data

Limiting max connections on backends and warn user

Hello, I'm currently testing a quite simple setup. Haproxy in front of 1 nginx and 3 backends running a node.js application. Nginx serves static files only and I have no issue with it. There are 2 frontends, one for http and one for https. In a standard configuration the browser will ask for a