How are URL redirects implemented in Arc XP?

What methods are available to redirect requests for content to alternate URL's in Arc XP, and when should these methods be used?

Arc XP provides two primary methods for implementing 301 and 302 redirects in Arc XP, Web Delivery Redirect UI and Draft API redirects:

Redirect UI

Redirect UI is found in Arc XP under Arc Home > Delivery.

Redirect UI is used to create both 301 and 302 redirects using the Arc XP user interface, and requires minimal technical knowledge. Redirect UI supports both the use of full URL’s and regular expressions (regex).

This method is often the fastest and most user friendly way of setting up a redirect. Redirect UI is especially useful for quickly setting up vanity redirects for pages or when changes to a specific redirect must be performed often or by staff with limited technical knowledge of API’s and Arc XP Resolvers.

Draft API & Resolver

Redirects can be implemented using a call to draft API and the use of a resolver to capture matching requests to Content API.

Redirects using Draft API require an understanding of how to interact with Draft API and how to set up resolvers. However, this method allows for automated creation and management of a large number of redirects. This method also prevents the Redirects UI from becoming cluttered with large numbers of redirects. For these reasons, draft API is often the method of choice when setting up redirects for Stories.

Additional Methods

Additional methods for implementing redirects are available to assist you in meeting your technical needs, including custom content sources and origin redirects. However, the use for these methods is very limited and the Redirect UI and Draft API methods should be fully explored before pursing further. If these methods are not meeting your needs, contact Arc XP.