RE: Seeking Guidance: 2.1.0 Config Error

Hello Aleks and Tim, Thank you for your insightful guidance on the usage of http-request and http-response in our context. We are updating the config files—several of them--along the lines you have suggested. We will test it and will push it into production shortly. Thank you. Sincerely,

Re: PATCH] BUG/MINOR: ssl: fix SSL_CTX_set1_chain compatibility for openssl < 1.0.2

On Fri, Nov 29, 2019 at 12:17:58PM +0100, Emmanuel Hocdet wrote: > > Hi, > > A forgotten fix, comment updated. > > ++ > Manu > > Thanks, merged. -- William Lallemand

Re: Duplicate headers created with set-header

Awesome, thanks for the fast turnaround. B. > On 29 Nov 2019, at 11:04, Christopher Faulet wrote: > > Le 29/11/2019 à 10:46, Robert Samuel Newson a écrit : >> Hi, >> I've discovered it is possible to make haproxy (2.0.9 and 2.0.10, at least) >> produce duplicate headers using the set-header

PATCH] BUG/MINOR: ssl: fix SSL_CTX_set1_chain compatibility for openssl < 1.0.2

Hi, A forgotten fix, comment updated. ++ Manu 0001-BUG-MINOR-ssl-fix-SSL_CTX_set1_chain-compatibility-f.patch Description: Binary data

Re: Duplicate headers created with set-header

Le 29/11/2019 à 10:46, Robert Samuel Newson a écrit : Hi, I've discovered it is possible to make haproxy (2.0.9 and 2.0.10, at least) produce duplicate headers using the set-header directive (which is defined as "This does the same as "http-request add-header" except that the header name is

Duplicate headers created with set-header

Hi, I've discovered it is possible to make haproxy (2.0.9 and 2.0.10, at least) produce duplicate headers using the set-header directive (which is defined as "This does the same as "http-request add-header" except that the header name is first removed if it existed."). This only happens when