-
F5 XC user identification based on WAX TS cookie and Shape security Bot Device ID +.
The user identification rules include headers, TLS fingerprints , ip addresses etc. but not the XC WAF generated TS session cookie and this session cookie is available on F5 AWAF/ASM for session tracking. If the WAF is licensed on XC this will be ...0
-
CE - the downstream TLS failures(i.e. client to the LB) are not exposed to the user
As customer using F5 volterra cloud with customer edge site I am unable to monitor the client failures at lower layers the layer 7. This fact make us blind at server side and we cannot react proactively. We are sentenced only on user feedback or s...0
-
Signature change log - search field + full signature list
IHAC that is asking for more details about a signature ID (ID 200004124) . Issue: the Signatures Changelog page does not show the expected signature in the page (CTRL+F does not work), the customer has to browse each change log date. More, the sig...0
-
Dynamic way to determine to create route-table for existing subnet (inside and workload)
Jeff Giroux had raised this issue, this will be a good requirement for cloud connector I need a way to specific existing route table. Or preferrably, do NOT add a route table.In reference to...resource "volterra_aws_vpc_siteI'm running a lab and s...
0
-
redacted
No description provided0 Will not implement
-
redacted
No description provided -
redacted
No description provided -
redacted
No description provided -
API Validation - custom Blocking page
The custom reponse page defined in the App fw policy or in the HTTP LB is not used by API Validation. The response page is a HTML page.My customer expect a JSON response in order to be handled by the client App.Could we have the ability to define ... -
make an anti-virus scanning feature available to apply to a specific API as a config on an LB similar to rate limiting or bot protection
even if it means upgrading licensing to pay for additional features, being able to enforce AntiVirus file upload scanning for specific APIs as a quick 2 or 3 step config directly on the Load Balancer just like enabling rate limiting or Bot Protect...0