-
Enhancement to HTTP header processing
Currently, we only support a limited set of http header processing documented in https://docs.cloud.f5.com/docs/how-to/advanced-security/configure-http-header-processing. Customer require further details of those information which currently availa...
2
-
Clarity on usage
Currently, if you want to understand your usages across different namespaces you need to run API queries to fully understand what apps are using what and how that is compared against your quota. This is not a very business savvy process because it...1 Planned
-
allow more than 4 IP Prefix Sets per service policy
Today the console limits the user to 4 IP Prefix Sets per service policy. So for example if you have call centers in the Philippines and other countries and want to allow them through based on IP range instead of allowing the entire country you ca...1
-
Trigger XC Malicious Users Javascript/Captcha based on IP Reputation/intelligence or threat mesh
The always-on javascript/captcha to be triggered if a source ip is marked bad by threat mesh or ip reputation.0
-
unique ports for origin pool members
I have a customer that has requested the ability to have multiple origin pool servers with different ports. They are currently BIG-IP customers and so they expect this kind of ability. In their case, they want to have multiple FQDN's target the sa...0
-
Visibility of fingerprints of the cert and private key in F5 XC
Is it possible to see fingerprints in F5 XC console of cert and private key as I can see them in browser?0
-
Add Route feature in TCP LB
Currently the TCP LB seems not support Route feature as HTTP LB. Please add this feature so we can use the TCP LB integrate with port range to forward the traffic to specific origin pool1 Planned
-
Simply backup all Volterra configuration (or per namespace)
I need to simply export all configuration (http load balancers, ip prefix sets, service policy, origin pool, health check, certificates, etc)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... -
F5XC - WAF - WAF exclusion rules in Shared Namespace
Currently, the WAF exclusion rule set is a key in a HTTP LB object. However, a lot of Apps can be developped on a same framework, so these apps can have a same False Positive / WAF exclusion rule and already known before deploying a LB. WAF exclus...
1