-
Client Side Defense - Add ability to filter by IP address on "Script List" dashboard
For troubleshooting purpose, it would be handy to have the ability to filter by IP on "Script List" dashboard. This will enable admin to identify users affted by the malicious script.0
-
Granular reports for WAF/BOT/DDOS activity
It would better enable customers to visualize specific traffic patterns and block patterns of F5. Often times these high-level reports are generated regularly to track changes and show long winded changes in risk over time. An example would be; "S...0
-
Support HTTP/3
Add HTTP load balancer support for HTTP/3 on client connections.0
-
DNS LB Should Support Private IPs via Site (CE) for Pool Members
Many GSLB use-cases are internal-facing. XC DNS supports adding private IPs for records but DNS LB requires public IP for pool members. Ideally, DNS LB would support private IPs being mapped to a site similar to HTTP LB origin pools and health mon...1
-
Create custom API groups
To be able to create more specific roles. For example one requirement that we have is for devops users to be able to create WAF exclusion rules. Desire is not to have access to change anything else on the LB.0
-
Allow searching of matching criteria within route rule configuration
Currently the search function at the top of the Routes only searches the pool name assigned to each rule. It does not allow you to search for values in the header for example. If a rule has a Host header match you cannot search for that domain.0
-
Location HTTP response header rewriting
For example, nitass.ddns.net is origin FQDN. proxy-2.nitass.com is LB FQDN. The origin returns 301 redirect with http://nitass.ddns.net/newlocation but user expects http://proxy-2.nitass.com/newlocation . # curl -I http://159.60.140.120/oldlocatio...0
-
Brute Force and Malicious User - skip processing except for the login page
Context After having detecting and mitigating a automation request with Bot Defense, Malicious User (MU) can prevent any further automation request from the same User Identifier. The benefit is that MU doesn't charge mitigated requests but Bot Def...0
-
injecting JA4 TLS fingerprint into every HTTP request as header
I'd like to inject the Ja4 tls fingerprint as a request header into every request sent to the origin. why: to have a relatively unique signature we can track that will be included in all the stacks upstream for correlation and to allow upstream ac...0 Planned
-
LB HTTP health monitor - no receive string
XC's synthetic monitors include the capability to specify a regex pattern against response body. This is helpful in general for targeted probing, i.e. common application-side built-in health checks that report on critical backend system resources/...0