[PATCH] DOC: config: added optional rst-ttl argument to silent-drop in action

This patch adds the optional silent-drop rst-ttl argument to the action lists in 5 places in the configuration manual. It should be backported to 2.7. I'll send you a patch for 2.7 when this one is accepted to save you from legwork, if requested. Best regards Mathias Weiersmueller cyberheads

[PATCH] MEDIUM: frontend: add parameter rst-ttl to silent-drop

Hi, I've accepted Willy's challenge from HAProxy.conf 2022, here is my shot: The silent-drop action was extended with an additional optional parameter, [rst-ttl ], causing HAProxy to send a TCP RST with the specified TTL towards the client. With this behaviour, the connection state on your

[PATCH] DOC: fix TOC in starter guide for subsection 3.3.8. and 3.4.9

Dear all, The subsection 3.4.9 (Standard features : Statistics) in the starter guide from 2.4 up to latest points to a non-existing anchor. It looks like this subsection was moved from 3.4.9 to 3.3.8 (Basic features : Statistics), but the TOC was not updated accordingly. Please check the

Re: payload inspection using req.payload

Hi Micha, > My problem is that the "req.payload(0,10)" fetch, which I am using for > that purpose, does not seem to reliably have access to the payload at > all times. The problem is not the fetch per se, it is the timing of the evaluation of the rule: tcp-request content rules are evaluated

Re: [PATCH] DOC: clarify matching strings on binary fetches

Willy, Will I (pardon the pun) send backported patches for the documentation for versions 1.5 - 2.1? Or is that handled by you? Regards Mathias From: Willy Tarreau Sent: Tuesday, December 3, 2019 07:35 To: Mathias Weiersmüller (cyberheads GmbH) Cc: haproxy

[PATCH] DOC: clarify matching strings on binary fetches

Documentation patch provided - I would backport it all the way down to 1.5 as it might save from headaches. Best regards Mathias > > It would be nice when you send us a patch to fix the doc. > > Regards > Aleks > > Nov 30, 2019 11:35:24 AM Mathias Weiersmü

RE: substring matching stops on a Null byte (\0) in a binary fetch

(CCing Thierry Fournier as maintainer of the pattern matching part) > We use HAProxy in TCP Mode for non-HTTP protocols. > > The request of one particular protocol looks like this: > - length of message (binary value, 4 bytes long) > - binary part (40-200 bytes) > - XML part > > Goal: We

substring matching stops on a Null byte (\0) in a binary fetch

Dear list! We use HAProxy in TCP Mode for non-HTTP protocols. The request of one particular protocol looks like this: - length of message (binary value, 4 bytes long) - binary part (40-200 bytes) - XML part Goal: We want to use a particular backend when the XML part of the request