> On Mon, May 28, 2018 at 01:43:41PM +0100, Jonathan Matthews wrote:
>> Improvements and suggestions welcome; flames and horror -> /dev/null ;-)
>
> Would anyone be interested in adding two new converters for this,
> working exactly like base64/b64dec but with the URL-compatible
> base64 encoding
Hi,
I'm wondering if there is any ongoing development or improvement plans
around the 'show errors' functionality?
This has come out of cases where we upgraded HAProxy 1.8 -> 2.2, and
$work customers started reporting requests that previously worked fine
now return 400 Invalid Request errors.
BYOB (Bring Your Own Board!)
"Join us to receive new major gifts funding for your important mission."
~ Stefanie Stark
VISIT HERE or
press PLAY BUTTON below for 60 Second Video Overview
"Major Gifts Ramp-Up is the single greatest virtual conference event
I've experienced since the start of
On Thu, Apr 01, 2021 at 02:26:07PM +0200, William Lallemand wrote:
> On Thu, Apr 01, 2021 at 10:19:31AM +, Jarno Huuskonen wrote:
> > Hello,
> >
> > I'm seeing a regression with 2.2.12 and using rsa and ecdsa certs on bind.
> > (cert1.pem.ecdsa
> > cert1.pem.ecdsa.ocsp
> > cert1.pem.ocsp
> >
On Thu, Apr 01, 2021 at 10:19:31AM +, Jarno Huuskonen wrote:
> Hello,
>
> I'm seeing a regression with 2.2.12 and using rsa and ecdsa certs on bind.
> (cert1.pem.ecdsa
> cert1.pem.ecdsa.ocsp
> cert1.pem.ocsp
> cert1.pem.rsa
> cert1.pem.rsa.ocsp
> )
>
Thanks for the report, I can reproduce
ash also doesn't happen on 2.2.10, 2.2.11, 2.3.9 and 2.4dev(haproxy-ss-
20210401))
Git bisect points to this commit:
commit b87c8899d872843c12b3516ad51da84b22538d91
BUG/MINOR: ssl: Fix update of default certificate
Something like this config should be able to reproduce:
frontend FE_crash
6 matches
Mail list logo
