Hi Dirkjan,
On Thu, Nov 22, 2018 at 11:41:11AM +0100, Dirkjan Bussink wrote:
> Hi Willy,
>
> > On 20 Nov 2018, at 16:19, Willy Tarreau wrote:
> >
> > Indeed it's already been two months, it would be the right time to emit
> > a new one. But at the moment all the people able to work on this are
Hi Willy,
> On 20 Nov 2018, at 16:19, Willy Tarreau wrote:
>
> Indeed it's already been two months, it would be the right time to emit
> a new one. But at the moment all the people able to work on this are
> fully loaded finishing their respective parts for 1.9 (or fixing it).
> Are you missing
Hi Dirkjan,
On Tue, Nov 20, 2018 at 04:13:47PM +0100, Dirkjan Bussink wrote:
> Hi Willy,
>
> > On 23 Oct 2018, at 14:48, Willy Tarreau wrote:
> >
> > You're right. I started backporting fixes for it last week. I think it
> > would make sense to make one "soon" (maybe next week-end along dev5).
Hi Willy,
> On 23 Oct 2018, at 14:48, Willy Tarreau wrote:
>
> You're right. I started backporting fixes for it last week. I think it
> would make sense to make one "soon" (maybe next week-end along dev5).
> In the mean time you can pick the latest maintenance snapshot if you
> want, it already
Hi Dirkjan,
On Tue, Oct 23, 2018 at 02:22:08PM +0200, Dirkjan Bussink wrote:
> Hi all,
>
> > On 21 Oct 2018, at 21:05, Willy Tarreau wrote:
> >
> > The support for TLS 1.3 ciphersuites was merged. If you play with it,
> > please report successes or failures, as this was backported to 1.8.
> > R
Hi all,
> On 21 Oct 2018, at 21:05, Willy Tarreau wrote:
>
> The support for TLS 1.3 ciphersuites was merged. If you play with it,
> please report successes or failures, as this was backported to 1.8.
> Regarding TLS, certificates can now be generated on the fly on
> BoringSSL as well.
Is there
Hi Willy.
Am 23.10.2018 um 10:55 schrieb Willy Tarreau:
> Hi Aleks,
>
> On Tue, Oct 23, 2018 at 10:23:43AM +0200, Aleksandar Lazic wrote:
>>> I'm not sure what you mean because the basic stuff (http actions, fetching
>>> samples, ACLs etc) will be OK. What will definitely not be ready will be to
Hi Aleks,
On Tue, Oct 23, 2018 at 10:23:43AM +0200, Aleksandar Lazic wrote:
> > I'm not sure what you mean because the basic stuff (http actions, fetching
> > samples, ACLs etc) will be OK. What will definitely not be ready will be to
> > have a TCP frontend connecting to an HTTP backend, "tcp-req
Hi.
Am 23.10.2018 um 09:49 schrieb Willy Tarreau:
> Hi Pavlos,
>
> On Tue, Oct 23, 2018 at 09:42:26AM +0200, Pavlos Parissis wrote:
>>> While we won't be doing anything specific for gRPC, my previous reading of
>>> the spec taught me that if we simply support H2 end to end it *should* work.
>>
>>
Hi Pavlos,
On Tue, Oct 23, 2018 at 09:42:26AM +0200, Pavlos Parissis wrote:
> > While we won't be doing anything specific for gRPC, my previous reading of
> > the spec taught me that if we simply support H2 end to end it *should* work.
>
> So, haproxy wont be able to understand services and calls
On 10/22/18 11:15 AM, Willy Tarreau wrote:
> Hi Pavlos!
>
> On Mon, Oct 22, 2018 at 11:01:37AM +0200, Pavlos Parissis wrote:
>> On 10/21/18 9:05 PM, Willy Tarreau wrote:
>>> Hi,
>>>
>>> HAProxy 1.9-dev4 was released on 2018/10/21. It added 97 new commits
>>> after version 1.9-dev3.
>>>
>>> There's
Hi.
Am 21.10.2018 um 21:05 schrieb Willy Tarreau:
> Hi,
>
> HAProxy 1.9-dev4 was released on 2018/10/21. It added 97 new commits
> after version 1.9-dev3.
New Docker Image available.
https://hub.docker.com/r/me2digital/haproxy19/
##
HA-Proxy version 1.9-dev4 2018/10/21
Copyright 2000-2018 Will
Hi Pavlos!
On Mon, Oct 22, 2018 at 11:01:37AM +0200, Pavlos Parissis wrote:
> On 10/21/18 9:05 PM, Willy Tarreau wrote:
> > Hi,
> >
> > HAProxy 1.9-dev4 was released on 2018/10/21. It added 97 new commits
> > after version 1.9-dev3.
> >
> > There's not much user-visible here, it's mostly another
On 10/21/18 9:05 PM, Willy Tarreau wrote:
> Hi,
>
> HAProxy 1.9-dev4 was released on 2018/10/21. It added 97 new commits
> after version 1.9-dev3.
>
> There's not much user-visible here, it's mostly another merge of some
> pending infrastructure changes. The most sensitive changes consist in
> th
14 matches
Mail list logo