Re: Set information in ClientHello TLS Extension as header

2021-07-10 Thread Willy Tarreau
Hi Michael, On Sat, Jul 10, 2021 at 09:03:40AM +0200, Michael Stiller wrote: > Hi List, > > we have the following issue to solve: > > A client puts some data value into a TLS Extension section (reserved or > arbitrary id) in the ClientHello packet. I want to read this value and set a > request

Re: Long broken option http_proxy: should we kill it ?

2021-07-10 Thread Aleksandar Lazic
On 08.07.21 19:44, Aleksandar Lazic wrote: On 08.07.21 18:33, Willy Tarreau wrote: Hi all, Amaury discovered that "option http_proxy" was broken. I quickly checked when it started, and it got broken with the introduction of HTX in 1.9 three years ago. It still used to work in legacy mode in

[PR] fix: TYPED_DATA typos for UINT64

2021-07-10 Thread PR Bot
Dear list! Author: Willem van der Schyff Number of patches: 1 This is an automated relay of the Github pull request: fix: TYPED_DATA typos for UINT64 Patch title(s): fix: TYPED_DATA typos for UINT64 Link: https://github.com/haproxy/haproxy/pull/1316 Edit locally: wget

Set information in ClientHello TLS Extension as header

2021-07-10 Thread Michael Stiller
Hi List, we have the following issue to solve: A client puts some data value into a TLS Extension section (reserved or arbitrary id) in the ClientHello packet. I want to read this value and set a request header with that value which should be available to the backend which is designated to