-
Requesting TRACK method to be added to Load Balancer 'Routes' as an available HTTP Method and Service Policy 'Rules' for Request Match under Method List
IHAC that needs to implement a condition that checks the request method of the incoming HTTP request, specifically for the TRACK method. The TRACK HTTP request method is rarely used but can often expose potential security vulnerabilities (e.g., Cr...0
-
Select Origin server based on performance metric
Ability for XC platform to select the faster member in the origin pool. If there are 3 members in the origin pool, XC selects the one with the lowest latency. The BIG-IP LB method "fastest(node)" would be the intended behavior
0
-
Service name isolation in K8s Site type
Ability to restrict access to services advertised into a K8s site type, but limiting requests from specific service names
0
-
Extended Verification certs (i.e. class 3 certificates)
Customers require class 3 certificates and currently have to provide and manage their own. Please enhance Distributed Cloud certificate services to use class 3 certificates.0
-
Increase the SAN limits to match Lets Encrypt
The auto cert feature only allows 32 SAN entries. XC should support what Lets Encrypt supports i.e. 100 SAN entries should be allowed.0
-
CE as a forward proxy to detect API calls from their internal server towards external API endpoints (egress)
The SecOps team is unaware of the types of API calls being sent to external API endpoints. These could include calls from a compressing server to outbound C2C servers. The customer is considering implementing a CE as a forward proxy to detect and ...0
-
DNS Requests Telemetry and Graphs
This is to add DNS Based traffic graphs / Telemetry to get a fair idea of number of DNS requests hitting the domain.0
-
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