-
Add the option "Request Body Handling: Do nothing" in the XC service policy
As seen on F5 sometimes by mistake it checks binary file uploads with signatures and to not stop completely the WAF this is the workaround. Examples: https://my.f5.com/manage/s/article/K38690758 https://my.f5.com/manage/s/article/K320814910
-
Request tagging
A user should be able to have tags applied to requests based on request characteristics, in order to visualize those requests in a report or dashboard.0
-
Disable Header Normalization on Request Headers
Currently, we have path normalization on the HTTP LB and header normalization on other settings of the origin pools (default or proper case). We should allow customers the flexibility to disable request header normalization as a whole, within the ...0
-
Customer exposed ability to gather un-sampled Performance and Application Data from XC
AWS has AWS VPC Flow Logs which allows customers to look at unsampled traffic data. GCP has VPC flow logs which is sampled, however they have Traffic mirroring which is unsampled Microsoft Azure also has something similar. The BIG-3 cloud provider...
0
-
Access needs to be provided only for specific service
Users want to access only specific service in console and other services should be blocked. For Example - Set of users want to use WAF based services but not the Cloud services and vice-versa for the other set of users. Looking for a specific feat...0
-
ddos & transit: view ddos graph's for ip's behind volumetric protection + more detail
ddos attacks are only visibile for ip's behind the scrubbing bgp session, and not for ip's behind the "bypass/volumetric" protection. insight's for the bypass/volumetric protection are very usefull to correlate attack's against other problems insi...0
-
Add Copy button on JSON config view
Easy solution to improve usability by having a button to copy json configuration1
-
Support requests that does not use SNI
We'd like to be able to communicate properly with tools that does not support SNI (here, for an example, our DNS traffic manager), so it would be great if VoltMesh was able to support these requests.0 Planned
-
Save log filter
Add the ability to save a log search filter, so that it is available even after the user reconnects. Possibility to share these filters between users.0
-
Metrics of origins pools , to see traffic and request at graph level and to add in Dashboard.
Considering adding some dashboard statistics for Origin Pools to the Performance Dashboard for LB. It would be a convenient way to easily find the amount of traffic or requests being handled for each origin, similar to the BIG-IP.0