Forum Discussion
NimbostratusF5 XC and Service Policy/HTTP path
Yes that is the limit in a XC service policy rule just make more rules in the same service policy with allow action each having 16 urls. Make one 1 default deny rule at the end. You can use "Next policy" action if you want other checks like geolocations etc. in a service policy after this one. Make certain to have allow all policy at the end if you are chaining multiple policies.
Keep in mind that a wildcard url for example /test/* is migrated with the service policy prefix match option. If the wildcard it at the start */test/ use suffix match and if it is in the middle then regex match will be needed like /te.*st/
Also this is a static feature and I recommend checking XC API discovery/protection that will learn the allowed URL API paths.
MVPYes that is the limit in a XC service policy rule just make more rules in the same service policy with allow action each having 16 urls. Make one 1 default deny rule at the end. You can use "Next policy" action if you want other checks like geolocations etc. in a service policy after this one. Make certain to have allow all policy at the end if you are chaining multiple policies.
Keep in mind that a wildcard url for example /test/* is migrated with the service policy prefix match option. If the wildcard it at the start */test/ use suffix match and if it is in the middle then regex match will be needed like /te.*st/
Also this is a static feature and I recommend checking XC API discovery/protection that will learn the allowed URL API paths.
