Redirect URL validation uses the DefaultEditor. The server-side validation determines if the URLs are unique by comparing it against the current site base and alternative URLs, as well as against all other sites’ site base URLs and alternative URLs.
If a site’s redirect URL property value (Pre-Opening, Post-Closing, or Site Disabled) contains a string that matches that site base URL (or any alternative URL), the browser will be redirected to the same site context, which will perform another redirect. The cycle will repeat until the user makes an appropriate browser action, such as a close request. This condition may also occur when a redirect URL points to another site’s site base or alternative URL that is also redirecting.
To avoid these possible infinite loop scenarios the following validation rules apply:
Redirect to current site - When a redirect, site base or alternative URL is created or amended, the system validates that there is no duplication between the redirect URLs and the main (site base and alternative) URLs. If a duplicate is detected, the system returns an error message and will not allow the URL to be saved.
Redirect to other site - When a redirect URL is created or amended the system compares the URL to all existing site base and alternative URLs. If a match is found, the system determines the site state for the matching site. If the site state is not
Enabled, the system returns an informative warning message alerting the user to the implications of redirecting users to a site that may in turn redirect the user or return an error.
If any of the redirect URLs do not contain a URL, a 404 Server Not Found error will occur.
