-
make an anti-virus scanning feature available to apply to a specific API as a config on an LB similar to rate limiting or bot protection
even if it means upgrading licensing to pay for additional features, being able to enforce AntiVirus file upload scanning for specific APIs as a quick 2 or 3 step config directly on the Load Balancer just like enabling rate limiting or Bot Protect...0
-
Service Policy to skip DDoS, IP Reputation, API Protection, etc
currently, a service policy can skip App firewall processing, skip bot processing, and skip Malicious User Mitigation. It cannot skip API Protection, DDos Protection, IP Reputation, Open API Specification Validation. This would have to be added ma...0
-
Please add the ability to automatically switch LB settings to Do Not Advirtise when all pods become unhealthy.
Even if all pods become unhealthy due to Health Check Fail, LB does not stop VIP advertisements, so traffic continues to be sent to the LB on the side where all pods are unhealthy. F5XC responded that it is the specification behavior of F5XC that ...0
-
F5 XC remote log integration with QRadar
Customer would like to have XC remote log (security, access, request log) to be able to integrate with their QRadar SIEM0
-
No Domain information on Alerts
Customer is expecting to see the domain name on Alerts information because if the LB is having multiple domains it will be not easy to identify the domain name.Please treat this as urgent requirement.0
-
list routes including route name or description
The route list should have a description or name column to allow identification when multiple routes include multiple origin servers.0
-
allow route config to match on connecting client IP or ASN in addition to matching on request headers and adding custom request headers
A route config is already verify flexible in that it allows for matching on incoming request headers and the ability to add custom request headers or override request headers with custom values. In our case, we'd like to also match on the connecti... -
restrict http log retention in the system to 10 days to allow for more advanced log search capabilities
One reason to not allow advanced search functions on http requests or security events such as filtering by regex is to avoid cost associated to CPU intensive or memory intensive search criteria. If a tenant is comfortable with only having access t... -
one click icon beside each filter result record field that adds that field value to the filter as "in" or "not in"
In the performance search console, instead of having to manually add a filter, include two clickable icons beside each field that if clicked adds that value to the filter as either "in" or "not in". This reduces the time to generate the desired fi... -
allow for different API rate limit configs for the same API based on request header criteria
Allow for multiple API rate limits to be configured on a single API (domain, method, path) where the order tries to match the first config in the list. For example: GET to /order/stuff on www.mysite.com has a default rate limit of 20/min. GET to /...