Re: [PATCH] FEATURE: Adding MPTCP with option to disable it and fall-back to TCP

Hello Nicolas, Thank you for the feedback! On 24/04/2024 17:45, Nicolas CARPi wrote: > Hello, > > On 24 Apr, Dorian Craps wrote: >> This attached patch uses MPTCP by default instead of TCP on Linux. > The backward compatibility of MPTCP is indeed a good point toward > enabling it by default. N

Odd warnings when using "option forwarded"

I was just reading about the new "option forwarded" capability in 2.9, so I added it to my config and now I get warnings when checking the config. [WARNING] (253408) : config : parsing [/etc/haproxy/haproxy.cfg:45] : 'option forwarded' ignored because frontend 'web80' has no backend capabilit

Re: [PATCH] FEATURE: Adding MPTCP with option to disable it and fall-back to TCP

Hi Willy, Thank you for the feedback! On 25/04/2024 00:12, Willy Tarreau wrote: > Hi! > > On Wed, Apr 24, 2024 at 05:45:03PM +0200, Nicolas CARPi wrote: >> Hello, >> >> On 24 Apr, Dorian Craps wrote: >>> This attached patch uses MPTCP by default instead of TCP on Linux. >> The backward compatib

Re: Odd warnings when using "option forwarded"

Hi Shawn On 26/04/2024 18:34, Shawn Heisey wrote: > I was just reading about the new "option forwarded" capability in 2.9, > so I added it to my config and now I get warnings when checking the config. > > [WARNING]  (253408) : config : parsing [/etc/haproxy/haproxy.cfg:45] : > 'option forwarded'

Re: Odd warnings when using "option forwarded"

On 4/26/24 10:51, Aurelien DARRAGON wrote: This is expected because forwarded cannot be used on frontend unlike forwardfor: That's interesting, because I already had `option forwardfor except 127.0.0.1` in the frontend which works perfectly. Should that be in the backend too? I was trying

Re: Odd warnings when using "option forwarded"

> That's interesting, because I already had `option forwardfor except > 127.0.0.1` in the frontend which works perfectly. Should that be in the > backend too? No, it's OK to use forwardfor in frontend sections since it is historical behavior. But forwarded doesn't allow that and requires ex

Question on deleting cookies from an HTTP request

Hey folks I have found that there is no operator "del-cookie" in HAProxy to delete cookies from the request. (HAProxy does support the operator "del-header"). Can you explain why such an operator is not supported? Is it due to complexity? Due to performance? It will be great if you can share deta

Re: Question on deleting cookies from an HTTP request

Hi Lokesh. On 2024-04-27 (Sa.) 01:41, Lokesh Jindal wrote: Hey folks I have found that there is no operator "del-cookie" in HAProxy to delete cookies from the request. (HAProxy does support the operator "del-header"). Can you explain why such an operator is not supported? Is it due to comple