ot; I was not sure it would appeal :-)
>
> On 19 February 2018 at 07:26, Willy Tarreau wrote:
>
>> Hi David,
>>
>> On Mon, Feb 12, 2018 at 03:38:15PM +, David CARLIER wrote:
>> > -- Forwarded message --
>> > From: David CARLIER
>
2018 at 07:26, Willy Tarreau wrote:
> Hi David,
>
> On Mon, Feb 12, 2018 at 03:38:15PM +, David CARLIER wrote:
> > -- Forwarded message --
> > From: David CARLIER
> > Date: 12 February 2018 at 15:37
> > Subject: Plans for 1.9
> > To: w...@
Hi David,
On Mon, Feb 12, 2018 at 03:38:15PM +, David CARLIER wrote:
> -- Forwarded message --
> From: David CARLIER
> Date: 12 February 2018 at 15:37
> Subject: Plans for 1.9
> To: w...@1wt.eu
>
>
> Was thinking as a contrib work, making haprox
DNS over TCP :)
-- Forwarded message --
From: David CARLIER
Date: 12 February 2018 at 15:37
Subject: Plans for 1.9
To: w...@1wt.eu
Was thinking as a contrib work, making haproxy more fuzzer "compliant"
(AFL and LLVM/fuzzer for example) which would mean turning haproxy into a
sha
On Fri, Feb 09, 2018 at 02:13:07PM +1100, Igor Cicimov wrote:
> Hi Willy,
>
> On Fri, Feb 9, 2018 at 1:16 AM, Willy Tarreau wrote:
>
> Fred plans to bring SSL support to the peers among
> > other things, and is working on a regression testing suite (yeah!).
>
>
> Does this mean it will be poss
Hi Willy,
On Fri, Feb 9, 2018 at 1:16 AM, Willy Tarreau wrote:
Fred plans to bring SSL support to the peers among
> other things, and is working on a regression testing suite (yeah!).
Does this mean it will be possible to share the sessions tickets between
the peers?
Hi all,
I would have liked to send this ealier but 1.8 kept us quite busy for a
while.
Last year's development cycle went impressively well in my opinion, with
multiple teams being able to work in parallel without stepping too much
onto each others' toes, and bug fixes being batched thanks to the
8 matches
Mail list logo