-
Disable changing TTL value for NS on UI
Currently, UI is available for the user to change TTL value for NS. However, the changed value is always ignored. It makes the user confuse. Thus, I request to disable changing TTL value for NS on UI. -
Add integration with BIG-IP similar to iQuery for health checking of services
Today BIG-IP customers have an out of band method to inform the upstream GTM/DNS devices of the health of the services it is supporting (iQuery). XC DNS LB needs to have a similar mechanism to help determine health of services running on F5 device... -
Please add a confirmation popup or message
Please add a pop up confirmation when deleting resources such as load balancers, origin pool, tls certs, etc. It is hard to believe this basic alerting/confirmation is not part of this enterprise solution. -
tenant owner failed login audit log
hello please create audit log for failed login to tenant owner its important to us to make alert on soc for us there is only email to tenant owner but if we want to cc soc mail its not supported also -
HTTP Load Balancer: HSTS response header is missing includeSubdomains
Best practices are to include the includeSubdomains directive in HSTS header. When HSTS is enabled on an HTTP load balancers, includeSubDomains is missing from Strict-Transport-Security response header. Reference links: https://datatracker.ietf.or... -
Create an API Gateway, API management tool & API security solution to manage & protect APIs
Implement a full API Gateway within XC to provide API gateway functionality, management of customer APIs, and act as an API security solution. I.E. an XC one-stop shop for APIs. This would reduce or avoid tacking on other numerous API Gateway solu... -
Log failed client TLS handshakes
There are no records of failed TLS handshakes. We cannot see if clients are connecting to an HTTP load balancer with incompatible settings. Either include this in the request logs, or create a separate log view for it.Planned
-
Cookie Based Load Balancing from RE
From https://my.f5.com/manage/s/article/K000152647 : LB first choose origin pool, then checks cookie and it's hash inside chosen origin pool. Because of that, you can observe that requests from one client with stickiness cookie enabled can be load... -
Ability to remove expired cert from LB
Currently if a certificate is expired, it's not allowed to change it from the LB config, for example to add a new one or replace it object. You need to renew the cert but in some cases that's not desired/possible. -
In tenant search/request id, it would be beneficial to search on the last 4 strings of a Support ID.
In tenant search/request id, you need to put the entire request id (support id), it would be nice to be able to search on the last 4 characters like you can in ASM.
