When a user makes an HTTP request, that request will result in the Notify-User2 action being presented to the user, because the last action of the same type to be processed will take precedence. After the the user clicks the accept' link, policy will recognize that and re-process their request, remembering not to triger that same notification action. This time, the Notify-user1 policy is triggered, as it's not been used yet in this transaction.
This is reasonable and expected behavior from a policy perspective, however, it's very confusing to users, and likely not the behavior the proxy administrator expected. experience.
Blue coat does not recommend this type of policy configuration. Rather, if multiple Notification policies are required, it's best practice to identify the destination URLs or source user IDs or IP addresses to be used to trigger each action, and put those rules in the same layer in policy.
Imported Document ID: 000008379
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe