Re: Haproxy running on ipv6 and http-in/

2023-11-30 Thread Jarno Huuskonen
Hi, On Tue, 2023-11-28 at 16:29 +0100, Christoph Kukulies wrote: > I'm wondering why I see haproxy running on ipv6 (Ubuntu 22.04): > > Excerpt from haproxy.cfg: > > frontend http-in > #    bind *:80 >     bind :::80 v4v6 > #    bind *:443 ssl crt /etc/haproxy/certs/xx.pem  >     bind :::443

Re: [PATCH] DOC: config: add missing colon to "bytes_out" sample fetch keyword (2)

2023-11-30 Thread Willy Tarreau
On Thu, Nov 30, 2023 at 08:15:32PM +0100, Tim Duesterhus wrote: > This reapplies 1eb049dc677f2de950158615ed3d8306ee5102d6, as the change was > accidentally reverted in 5ef48e063ecf992646c7af374153f106050fb8ec. Oops, thanks for catching this one, Tim! Now applied, thank you! Willy

[PATCH] DOC: config: add missing colon to "bytes_out" sample fetch keyword (2)

2023-11-30 Thread Tim Duesterhus
This reapplies 1eb049dc677f2de950158615ed3d8306ee5102d6, as the change was accidentally reverted in 5ef48e063ecf992646c7af374153f106050fb8ec. --- doc/configuration.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/configuration.txt b/doc/configuration.txt index 9d3d92d276

[ANNOUNCE] haproxy-2.9-dev12

2023-11-30 Thread Willy Tarreau
Hi, HAProxy 2.9-dev12 was released on 2023/11/30. It added 106 new commits after version 2.9-dev11. It looks like we're getting good for the release. That's a last -dev to help testers rebase and get all the fixes but quite frankly we could very well have released this one. Let's first get rid

[PATCH 1/3] REGTESTS: sample: Test the behavior of consecutive delimiters for the field converter

2023-11-30 Thread Tim Duesterhus
This is in preparation of a follow-up patch to fix the word converter. --- reg-tests/converter/field.vtc | 4 1 file changed, 4 insertions(+) diff --git a/reg-tests/converter/field.vtc b/reg-tests/converter/field.vtc index 1243728c01..3b1d8198e3 100644 --- a/reg-tests/converter/field.vtc +++

[PATCH 2/3] BUG/MINOR: sample: Make the `word` converter compatible with `-m found`

2023-11-30 Thread Tim Duesterhus
Previously an expression like: path,word(2,/) -m found always returned `true`. Bug exists since the `word` converter exists. That is: c9a0f6d0232cf44d6b08d1964b9097a45a6c65f0 The same bug was previously fixed for the `field` converter in commit 4381d26edc03faa46401eb0fe82fd7be84be14fd. The

[PATCH 3/3] DOC: Clarify the differences between field() and word()

2023-11-30 Thread Tim Duesterhus
word() mentions that delimiters at the start and end are ignored, but it does not mention that consecutive delimiters are merged. May be backported as far as the patch applies. --- doc/configuration.txt | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/doc/configuration.tx