-
To provide a customer accessible button to acknowledge or clear site alerts
Allow customers to acknowledge or dismiss a Site Heartbeat Down alert. Support clearing alerts associated with decommissioned or replaced nodes. Ensure that acknowledging the alert does not affect the replacement nodes or the existing site con... -
Custom Error Page for HTTP 421 Misdirected Request
Currently when XC returns an HTTP 421 error due to HTTP/2 connection re-uses: Connection Coalescing: In HTTP/2 or HTTP/3, the browser or client reuses an existing TLS connection for a different domain, but the target server is not configured to ha... -
Enhance CE upgrade procedure and create rollback procedure
We had a production incident after upgrading a CE cluster. The CE nodes couldn't communicate with the backends. We would like to have the possibility to upgrade only one node of the cluster and test if the application traffic is still flowing norm... -
Rate Limit custom response page
Without it, clients that are hit with the limit are left clueless on how to contact us. -
F5 XC HTTP Load Balancer – Display Configured FQDN in WAF Exclusion Rules Domain Column
Feature Area: Web App & API Protection → HTTP Load Balancer → WAF Exclusion Rules Request Type: GUI Enhancement / Usability Improvement Description When viewing the WAF Exclusion Rules configured under an HTTP Load Balancer in the F5 Distribut... -
Provide key exchange logging via Console and GLR logs
The current GLR and console logs do log the TLS versions and SSL ciphers used in an inbound connection but it'd also be nice to see the key exchange used. Especially with more organizations adopting ML-KEM, we'd like to be able to represent that a... -
Certificate expiration alerting - Alerting needs to say the exact count of days before expiration
Currently certificate expiration alerts describe "TLS Custom Certificate for virtual host <name> expires in less than 15 days". Customer would like the exact number of days until expiration for each certificate to be reported rather than all...
-
API Protection/Validation - Allow empty values by default for non-mandatory discovered parameters/headers
Problem: When a parameter or header is identified through API Discovery and is not marked as mandatory, the system currently does not allow that field to accept an empty value by default. This forces users to manually edit the API definition just ... -
Provide the ability to toggle WAF base64 encoding on/off
Be able to define an exception or an option, so that customers can define something like: If FQDN == www.example.com && URI == /parent/directory/filename.com && Parameter == example --- THEN do not decode Base64
-
Provide Recommendations For XC configurations
Provide useful recommendations for items that could or should be configured, like health montiors or moving WAF from monitoring to blocking etc. See example attached
