Re: [PATCH] MEDIUM: sample: Modify fetchers for req.hdrs and res.hdrs to selectively include / exclude headers

Hi Ruei-Bang, On Fri, Nov 10, 2023 at 01:33:01AM +, Ruei-Bang Chen wrote: > Hi team, > > Based on the feedback from > https://www.mail-archive.com/haproxy@formilux.org/msg44153.html, I have > attached a patch for modifying fetchers for req.hdrs and res.hdrs to > selectively include / exclude

[PATCH] MEDIUM: sample: Modify fetchers for req.hdrs and res.hdrs to selectively include / exclude headers

Hi team, Based on the feedback from https://www.mail-archive.com/haproxy@formilux.org/msg44153.html, I have attached a patch for modifying fetchers for req.hdrs and res.hdrs to selectively include / exclude headers. I have the following 3 questions while I was doing this change: 1. Should I

Should we change the -c output?

Hello, haproxy -c seems to be too verbose in the systemd logs by showing "Configuration file is valid" for every reloads. Is there anyone against removing this message by default? This will still output the alerts and warnings if some exists but the "Configuration file is valid" message will only

??external-check?? does not work properly in Rocklinux8

hi,   1??docker pull haproxy:2.8.3    2??haproxy.conf??external-check command /var/lib/haproxy/test.sh    When the container is running in the RockLinux environment, the test.sh script is not called for execution. On the contrary, the Centos environment can be called and executed normally.    

Re: unsupported protocol family 2 for address 'quic4@0.0.0.0:4

> Am 08.11.2023 um 21:29 schrieb Shawn Heisey : > > On 11/8/23 10:11, Christoph Kukulies wrote: >> frontend web80 >> bind 0.0.0.0:80 name web80 >> default_backend be-local-81 > > Normally you definitely would not want this in your production config... > typically any request c