Any update on this?
On Mon, Jan 18, 2021, 3:56 PM Илья Шипицин wrote:
> we can do nasty thing.
> SSL_CLIENT_HELLO_CB is not defined for BoringSSL, we can (in
> openssl-compat.h) check whether BoringSSL is used and define that macro.
>
> I'm not sure it is good thing.
>
> if you thing it is,
Hello list, I'm configuring a couple of maps used to route requests based on
hostname and path. The map lay out is pretty much like this:
sub.tld/path1 name_backend1
...
I have some distinct ways to match a request: str, beg, dir, reg, using their
map converter derivatives.
Hello,
On Tue, 2021-01-19 at 15:40 +0530, Amol Arote wrote:
> After upgrading haproxy 2.3.2 we are facing the below ssl tls issue while
> connecting links internally, but when we check web browsing its auto
> getting tls 1.2 there is no such issue.when connecting internal links its
> not getting
Dear Team,
After upgrading haproxy 2.3.2 we are facing the below ssl tls issue while
connecting links internally, but when we check web browsing its auto
getting tls 1.2 there is no such issue.when connecting internal links its
not getting tls 1.2 its showing tls 1.0 and showing below error
NFP WORKSHOPS
Affordable Charity Training Courses
18 Blake Street, York YO1 8QG 01133 280988
Bid Writing: The Basics
ONLINE VIA ZOOM COST £95.00
TOPICS COVERED
Do you know the most common reasons for rejection? Are you gathering the right
evidence? Are you making the right
5 matches
Mail list logo
