Say Bye to Adwords – Grow with Our Organic Listing Plan

2018-11-26 Thread Darin Booth
Dear haproxy.com Team, Hope all well at your end! After a thorough check of your website, it came into notice that you trying to captivate more customers and dealing to developing your standpoint both internationally and locally. You run a sponsor listing on Google to build your image

Re: SSL certs

2018-11-26 Thread Alberto Oliveira
Hello Azim, HAproxy itself doesn't manage ssl certs so you should already have one, buy one or generate one for free using Let's Encrypt (https://letsencrypt.org/). You can find multiple sources to guide you on how to use ssl certs on haproxy:

Re: [PATCH] MINOR: ssl: free ctx when libssl doesn't support NPN

2018-11-26 Thread Willy Tarreau
On Mon, Nov 26, 2018 at 10:57:17PM +0100, Lukas Tribus wrote: > The previous fix da95fd90 ("BUILD/MINOR: ssl: fix build with non-alpn/ > non-npn libssl") does fix the build in old OpenSSL release, but I > overlooked that the ctx is only freed when NPN is supported. > > Fix this by moving the

RE: Enquiry

2018-11-26 Thread BRUNETTI ALBERTO FAKHRI
Kindly send us your price list or product catalog asap for trail order. Thanks Sales Manager. Informativa Privacy - Ai sensi del Regolamento (UE) 2016/679 si precisa che le informazioni contenute in questo messaggio sono riservate e ad uso esclusivo del destinatario. Qualora il messaggio in

SSL certs

2018-11-26 Thread Azim Siddiqui
Hello, Hope you are doing good. We are using HAproxy in our company. But the ssl certs has been expired. I want to renew it. As i can see HAproxy only takes .pem format for certs. So what files should be included in that .pem file ? And can you please tell me how to convert the certs in .pem ?

Re: OCSP stapling with multiple domains

2018-11-26 Thread Igor Cicimov
Hi Moemen, On Tue, Nov 27, 2018 at 1:24 AM Moemen MHEDHBI wrote: > > > On 11/14/18 1:34 AM, Igor Cicimov wrote: > > On Sun, Nov 11, 2018 at 2:48 PM Igor Cicimov > wrote: >> >> Hi, >> >> # haproxy -v >> HA-Proxy version 1.8.14-1ppa1~xenial 2018/09/23 >> Copyright 2000-2018 Willy Tarreau >> >>

[PATCH] MINOR: ssl: free ctx when libssl doesn't support NPN

2018-11-26 Thread Lukas Tribus
The previous fix da95fd90 ("BUILD/MINOR: ssl: fix build with non-alpn/ non-npn libssl") does fix the build in old OpenSSL release, but I overlooked that the ctx is only freed when NPN is supported. Fix this by moving the #endif to the proper place (this was broken in c7566001 ("MINOR: server: Add

1.7.11 with gzip compression serves incomplete files

2018-11-26 Thread Veiko Kukk
Hi! There is not much to add, just that it's been broken before in 1.7.9 and is again broken in 1.7.11. Works with 1.7.10. When applying patch provided here https://www.mail-archive.com/haproxy@formilux.org/msg27155.html 1.7.11 also works. Testing is really simple, just configure haproxy

Re: haproxy segfaults when clearing the input buffer via LUA

2018-11-26 Thread Moemen MHEDHBI
On 11/20/18 2:25 PM, Christopher Faulet wrote: > Le 17/11/2018 à 20:42, Willy Tarreau a écrit : >> Hi Moemen, >> >> On Wed, Nov 14, 2018 at 04:07:42PM +0100, Moemen MHEDHBI wrote: >>> Hi, >>> >>> I was playing with LUA, to configure a traffic mirroring behavior. >>> Basically I wanted HAProxy to

Re: OCSP stapling with multiple domains

2018-11-26 Thread Moemen MHEDHBI
On 11/14/18 1:34 AM, Igor Cicimov wrote: > On Sun, Nov 11, 2018 at 2:48 PM Igor Cicimov > > wrote: > > Hi, > > # haproxy -v > HA-Proxy version 1.8.14-1ppa1~xenial 2018/09/23 > Copyright 2000-2018 Willy Tarreau

Re: [PATCH] CLEANUP: http: Fix typo in init_http's comment

2018-11-26 Thread Tim Düsterhus
Willy, Am 16.09.18 um 00:42 schrieb Tim Duesterhus: > It read "non-zero" where it should read zero. > --- > src/http.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/src/http.c b/src/http.c > index 932f3cf7..1ca1805b 100644 > --- a/src/http.c > +++ b/src/http.c > @@

Re: BUG: Warning: invalid file descriptor -1 in syscall close()

2018-11-26 Thread William Lallemand
On Sun, Nov 25, 2018 at 08:04:14PM +0100, Tim Düsterhus wrote: > I've taken the usage from your commit message in commit > e736115d3aaa38d2cfc89fe74174d7e90f4a6976 :-) > Oh right, I edited the usage message in this patch but I forgot to edit the commit message when I rebased my patches :( --