regtest failure for /cache/h00000.vtc, config parsing fails? after commit 7805e2b

Hi Christopher, List A recent commit http://git.haproxy.org/?p=haproxy.git;a=commit;h=7805e2bc1faf04169866c801087fd794535ecbb2 seems to have broken config parsing for some configurations as seen with reg-test: /cache/h0.vtc Using: haproxy version: 1.9-dev8-7805e2b ***  h1    0.0 debug|[

Re: acme proxy for internal use

I've used Lua or Apache web server depending on the environment. Haproxy doesn't do this natively. Sent from Nine From: Joel Linn Sent: Saturday, December 1, 2018 4:17 PM To: haproxy@formilux.org Subject: acme proxy for internal use Hi

acme proxy for internal use

Hi, I want to use letsencrypt for services in my intranet. The acme protocol demands that a challenge response is published under http://certname.domain.tld/.well-known/acme-challenge/xyz All subdomains under domain.tld get forwarded from the internet to a haproxy on the intranet. What I need

Regarding PKCS#11 support with HAProxy

Hi, Please help me with followings: 1. Do the lastest verion of HAProxy supports PKCS#11 for cryptographic key storage ? 2. Is the patch on the mailing list from 2015 (here: 'https://www.mail-archive.com/haproxy@formilux.org/msg18806.html' ) still working/supported with HAPRox