On Fri, Aug 17, 2018 at 01:02:52AM +0200, Cyril Bonté wrote:
> Hi Willy and Sachin,
> Le 14/08/2018 à 01:27, Cyril Bonté a écrit :
> > Thanks for the feedback. I've made some tests with the lines of code you
> > suggested and it looks to work fine. I'll prepare the patches tomorrow.
Hi Willy and Sachin,
Le 14/08/2018 à 01:27, Cyril Bonté a écrit :
Thanks for the feedback. I've made some tests with the lines of code
you suggested and it looks to work fine. I'll prepare the patches tomorrow.
OK, some updates on the patch.
It was working well with haproxy 1.7, the same with
On 16.08.2018 20:15, Willy Tarreau wrote:
> Quite frankly, at the moment (in 2018) I see little value in using that many
> threads or even processes.
You're right; I didn't mention how many processes we're actually running
on these and how things are actually managed. Until reaching 20Gbps, we
On Tue, Aug 14, 2018 at 12:56:13AM +0100, Bertrand Jacquin wrote:
> In most cases, "TLSv1.x" naming is used across and documentation, lazy
> people tend to grep too much and may not find what they are looking for.
Thanks Bertrand. I retagged it to DOC since it only touches doc so
that we can
On Mon, Aug 13, 2018 at 02:07:57PM -0400, Patrick Hemmer wrote:
> This adds documentation that was missed as part of 268a707.
Oh thank you Patrick, I think I didn't even notice that the sample fetch
functions were already there :-)
On Wed, Aug 15, 2018 at 04:56:10PM +0200, J. Kendzorra wrote:
> I was looking into steering HAProxy to some underutilized cores on a multi
> processor system where both network interrupts as well as HAProxy are
> supposed to run on a specific numa node; the initial idea was to have
On Thu, Aug 16, 2018 at 03:48:22AM +0200, Angelo Höngens wrote:
> Hey guys,
> I'm building a solution where I am ssl-offloading some old plain http
> The http ports are listening on 8001, 8002, 8003, etc. I'm using haproxy
> 1.8.12 to listen on ports 18001, 18002,
could you please have a look at this one, I suspect Raghu's proposal
is reasonable, I just want to be sure we don't break DNS and friends.
On Mon, Aug 13, 2018 at 08:16:31PM +0530, Raghu Udiyar wrote:
> Hi Willy, Baptiste
> On Fri, 29 Jun 2018 at 08:12 Willy
On Tue, Aug 14, 2018 at 11:39:35AM +0200, Lukas Tribus wrote:
> Abhishek Gupta reported on discourse that set server [...] fqdn always
> fails. Further investigation showed that this requires the internal
> DNS resolver to be configured. Add this requirement to the docs.
> Must be
On Thu, Aug 16, 2018 at 03:25:57PM +0200, Emeric Brun wrote:
> Here two patches which should fix the issues.
Applied, thanks guys.
Both patches applied, thanks guys!
Olivier, I have a suggestion for this one :
On Thu, Aug 16, 2018 at 07:17:07PM +0200, Olivier Houchard wrote:
> From 90fc92f72c6b47d88769bb73680702d7b8e6 Mon Sep 17 00:00:00 2001
> From: Olivier Houchard
> Date: Thu, 16 Aug 2018 19:03:02 +0200
On Thu, Aug 16, 2018 at 05:50:27PM +0200, Olivier Houchard wrote:
> Hi Pieter,
> On Thu, Aug 16, 2018 at 12:24:04AM +0200, PiBa-NL wrote:
> > Hi List,
> > Anyone got a idea how to debug this further?
> > Currently its running at 100% again, any pointers to debug the process as
On Thu, Aug 16, 2018 at 12:24:04AM +0200, PiBa-NL wrote:
> Hi List,
> Anyone got a idea how to debug this further?
> Currently its running at 100% again, any pointers to debug the process as
> its running would be appreciated.
> Or should i compile again from current master and
Hi Willy, Michael,
On 08/02/2018 06:03 PM, Willy Tarreau wrote:
> Hi Michael,
> On Thu, Aug 02, 2018 at 03:48:13PM +0200, Michael Wimmesberger wrote:
>> while preparing to use multi-keytype bundles for my company's
>> domains, I found the following two issues:
> Thanks for
HI all! I'm compile modsec as described in the instructions
contib/modsec/README, but have the next errors:
# /usr/local/bin/modsecurity -n 4 -d -f /etc/haproxy/waf/modsecurity.conf
1534409877.286475  ModSecurity for nginx (STABLE)/2.9.2
Mail list logo