Hi,
This is a friendly bot that watches fixes pending for the next haproxy-stable
release! One such e-mail is sent periodically once patches are waiting in the
last maintenance branch, and an ideal release date is computed based on the
severity of these fixes and their merge date. Responses
Hello Tim,
On Thu, Oct 22, 2020 at 09:15:04PM +0200, Tim Duesterhus wrote:
> William,
> Rémi,
>
> I'm super happy to see that the support for if-none-match made it into 2.3. I
> already was considering poking under some of the recent -devX announcements,
> but thought it already was too late for
NFP WORKSHOPS
18 Blake Street, York YO1 8QG 01133 280988
Affordable Training Courses for Charities, Schools & Public Sector
Organisations
This email has been sent to haproxy@formilux.org
CLICK TO UNSUBSCRIBE FROM LIST
Alternatively send a blank e-mail to unsubscr...@nfpmail2001.co.uk
Good good good
On Tue, Oct 27, 2020, 5:10 PM William Lallemand
wrote:
> On Sat, Oct 24, 2020 at 11:51:57PM +0500, Илья Шипицин wrote:
> > Hi,
> >
> > "#ifdef SSL_READ_EARLY_DATA_SUCCESS" seem to be better
> > than version based check.
> >
> > it is preparation to unlocking BoringSSL 1.1.1
On Sun, Oct 25, 2020 at 07:37:16PM +0500, Илья Шипицин wrote:
> Hi,
>
> we missed couple of releases.
>
> Ilya
Merged, thanks.
--
William Lallemand
On Thu, 22 Oct 2020 at 16:18, wrote:
>
> Hi,
>
> Last release 1.8.26 was issued on 2020-08-03. There are currently 20
> patches in the queue cut down this way:
> - 10 MEDIUM, first one merged on 2020-08-05
> - 10 MINOR, first one merged on 2020-08-03
>
> Thus the computed ideal
On Sat, Oct 24, 2020 at 11:51:57PM +0500, Илья Шипицин wrote:
> Hi,
>
> "#ifdef SSL_READ_EARLY_DATA_SUCCESS" seem to be better
> than version based check.
>
> it is preparation to unlocking BoringSSL 1.1.1 compatibility version.
>
>
>
> cheers,
> Ilya
Totally agree with this, merged in
ping :)
сб, 24 окт. 2020 г. в 23:51, Илья Шипицин :
> Hi,
>
> "#ifdef SSL_READ_EARLY_DATA_SUCCESS" seem to be better
> than version based check.
>
> it is preparation to unlocking BoringSSL 1.1.1 compatibility version.
>
>
>
> cheers,
> Ilya
>
On Mon, Oct 26, 2020 at 02:32:20PM +0100, ehoc...@club-internet.fr wrote:
> Hi,
>
> It's a fix for a regression with OCSP and BoringSSL.
> OCSP work with BorginSSL, not at the same way than openssl, but it work:
> OCSP data is simply link to CTX context.
>
> ++
> Manu
>
>
>
Thanks, pushed
9 matches
Mail list logo