Re: AW: acl using fc_dst_port not working

2023-03-10 Thread Aurelien DARRAGON
You're welcome! The same bug was also found in the smp_fetch_dst_is_local() function (fc_dst_is_local sample fetch). Attached is the patch that addresses the 2 bugs, it will probably be included in the next batch of releases. 2.5 and 2.7 are also affected > Unfortunately, this option doesn't

AW: acl using fc_dst_port not working

2023-03-10 Thread Corin Langosch
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

Re: acl using fc_dst_port not working

2023-03-10 Thread Aurelien DARRAGON
Hi, > During my tests I can see in the logs that fc_dst_port is 8080. However, > the ACL isn't set to true. If I try the same with "acl test > fc_dst 127.0.0.2" it works as expected. However, this is not what I > need. I also tried different matchers like "acl test fc_dst_port -m int > 8080",

acl using fc_dst_port not working

2023-03-07 Thread Corin Langosch
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)