-
configure allowed egress domains in Client Side Defense (CSD) allowed list
why - Today CSD (Client Side Defense) mitigates on a per JavaScript/domain combo which means each time a new script or a new domain shows up we have to act to mitigate. It would be more efficient to define an allowed list of domains, domains JS is...0
-
Add custom VIP to virtual site reference in HTTP and TCP Load Balancers
I want to use the same custom VIP for a load balancer across multiple sites and I know I can simply add multiple site object references to the custom vip section of the http load balancer, but I'll need to do this for any new site added instead of...
3
Planned
-
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
-
service tags
Hello, i would like to have an F5 mainted list of service tags , for example from microsoft https://www.microsoft.com/en-us/download/details.aspx?id=56519 that i can integrate directly in the ip prefix list0
-
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
-
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
-
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