AW: acl using fc_dst_port not working

Hello Aurelien, thank you very much for your reply! Indeed, there is a bug in the function smp_fetch_dport(): conn_get_src() is used where conn_get_dst() should be used instead. Thank you for fixing it!  Thank you for telling us, I'm working on the patch Meanwhile, maybe "dst_port" could work as

acl using fc_dst_port not working

Hello I need to set an ACL when the request comes in at a particular port. I have the following configuration: frontend generic-http bind 127.0.0.1:80 bind 127.0.0.1:8080 accept-proxy bind 127.0.0.2:8080 accept-proxy acl test fc_dst_port 8080 http-request set-var(txn.acl_trigger)

AW: Understanding show table output and rate limiting weirdness

Hello Willy, thank you very much for your response and please excuse my very late reply!  On Aug 23, 2022 at 20:08, Willy Tarreau wrote: It makes me think that something is wrong with the date, though I can't imagine what. Is it entirely reproducible or does it happen spuriously ? I'm wondering

Understanding show table output and rate limiting weirdness

Hello guys, I’m using the docker image 2.5.7-2ef551d with basic rate limiting configured like this: backend test acl test_rate_limit_by_ip_exceeds_limit src,table_http_req_rate(test_rate_limit_by_ip) gt 5 http-request deny deny_status 429 if test_rate_limit_by_ip_exceeds_limit

AW: rate-limiting and retry-after header

Hello Jérôme, On 2022-06-20 13:43, Jérôme Magnin wrote: You can with an http-after-response rule. See https://cbonte.github.io/haproxy-dconv/2.5/configuration.html#http-after-response Or you can use an http-request return rule instead of deny/deny_status to set the status code and header with

rate-limiting and retry-after header

Hi guys, I'm using haproxy 2.5 and have some basic rate limiting configured like this (the actual configuration contains more rules for different urls): backend test acl rate_limit_by_ip_exceeds_limit src,table_http_req_rate(rate_limit_by_ip) gt 100 http-request deny

stats page enhancement idea

Hi all, I'd like to suggest to add min/max/avg response time for each backend on stats page. I think it'd help a lot in finding the proper settings of how to load balance the backends and easily check if everything is working as it should. What do you think? Corin

1.4.3 and statistics error

Hi! I just upgraded to 1.4.3 and noticed the new hover feature in the statistics. It looks nice, but the values confuse me a little: Queue Session rateSessionsBytes Denied Errors WarningsServer Cur Max Limit Cur Max Limit Cur Max Limit Total LbTot