The feature is missing because when a client will be block by the Service Policy he will know that the service's traffic is through F5 and which PoP is answering right now for the request. It's unsecure for some customers.
It would be far more flexible to offer the option to return custom HTTP codes for Service Policies, just like with WAP.
This would allow to override the returned pages through the custom error pages in any way deemed appropriate..
You can create custom error responses on LB with Service Policies under More Options, Configure Error Response Options, and create a Response for 403.
You won't be notified about changes to this idea.
It would be far more flexible to offer the option to return custom HTTP codes for Service Policies, just like with WAP.
This would allow to override the returned pages through the custom error pages in any way deemed appropriate..
You can create custom error responses on LB with Service Policies under More Options, Configure Error Response Options, and create a Response for 403.