Notify User page does not display
The Notify User page does not display even though a policy including a Notify User action exists.
This issue occurs when the destination URL redirects to another URL. For example, a URL might redirect to a URL in the user's local domain (e.g., www.google.com redirects to www.google.co.kr), or it might redirect permanently to a URL in a new location (e.g., mail.google.com redirects to accounts.google.com). In such cases, the origin content server (OCS) returns an HTTP status code that is not 200 (OK), such as 302 (Found).
The target URL must return a 200 status in order to avoid breaking its traffic.
To work around this issue, either modify the condition to match redirected URL or base the condition on the referer URL.
NOTE: The nature of this work around may require excessive maintenance depending on the number of target URLs you have in the list.
Rate this Page
Please take a moment to complete this form to help us better serve you.