URL Redirect

Applies To:

HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.

HTTP SmallLegacy. If you are currently serving traffic over this platform, then you may continue to do so. However, we recommend that you serve your traffic over our more robust HTTP Large platform.

ADNThe Application Delivery Network platform has been optimized to deliver dynamic content (e.g., login credentials, account information, etc.) over HTTP or HTTPS. Typically, user-specific and database-driven content are served over this platform.

Rules EngineAllows the customization of how requests are handled by our CDN service. It may be used to override the default response provided by an origin server, CDN settings, and the default edge server behavior. - Advanced

Category: URL

Purpose: Redirects requests via the Location header.

This capability requires Rules Engine - Advanced Rules which must be purchased separately. Contact your CDN account manager to activate it.

Configuration

The configuration of this feature requires setting the following options:

Option	Description
Source	Identify requests that will be redirected via a relative path. This relative path, which starts directly after the hostname in the CDN URL, is shown in blue font below. http://wpc.0001.edgecastcdn.net/800001/myorigin/path/file.ext Verify that the specified pattern doesn't conflict with the parent match conditions defined for this feature. Valid syntax varies according to the number of customer origins that you would like to match. Specific Origin: Match against a specific origin by specifying it via a content access pointThis URL segment of a CDN URL identifies where the request should be directed. This relative path starts directly after the CDN hostname. The proper syntax for a content access point is "/yyAN," where "yy" stands for the origin identifier and "AN" stands for a customer account number. A content access point for a customer origin also includes a directory that identifies it. followed by a regular expression for the desired path. Syntax: Content Access Point/Regular Expression Example: Match all requests to a customer origin called myorigin via the following syntax: /800001/myorigin/(.) Multiple Customer Origins: Match against multiple origins by delimiting each desired customer origin using a \|. Syntax: /80Account Number/(Origin 1\|Origin 2\|Origin N)/Regular Expression Example: Use this pattern to define a capture group that matches a customer origin group called marketing or sales: /800001/(marketing\|sales)/Regular Expression All Customer Origins: Match against all of your customer origins by specifying . or (.). Syntax: /80Account Number/(.)/Regular Expression Example: Use this pattern to define a capture group that matches all of your customer origins: /800001/(.*)/Regular Expression You may only define a customer origin using a literal value (e.g., marketing) or one of the regular expressions patterns defined above. All other regular expression syntax is disallowed when defining a customer origin. This limitation does not apply to the relative path defined after the content access point.
Destination	Define the URL path to which the above requests will be redirected. Dynamically construct this URL path using: A regular expression pattern HTTP variables You may not use response metadata (e.g., %{resp_ResponseHeader}) when constructing this path. It is highly recommended to use an absolute URLThis type of URL identifies a resource (e.g., asset or file) using the following format: scheme://server/path/resource (e.g., http://cdn.mydomain.com/sales/presentation.pdf).. The use of a relative URL may redirect CDN URLs to an invalid path. URL encoding should not be applied to the specified URL.
Code	Select the response code that will be returned to the requester.

Option

Description

Source

Identify requests that will be redirected via a relative path. This relative path, which starts directly after the hostname in the CDN URL, is shown in blue font below.

http://wpc.0001.edgecastcdn.net/800001/myorigin/path/file.ext

Verify that the specified pattern doesn't conflict with the parent match conditions defined for this feature.

Valid syntax varies according to the number of customer origins that you would like to match.

Specific Origin: Match against a specific origin by specifying it via a content access pointThis URL segment of a CDN URL identifies where the request should be directed. This relative path starts directly after the CDN hostname. The proper syntax for a content access point is "/yyAN," where "yy" stands for the origin identifier and "AN" stands for a customer account number. A content access point for a customer origin also includes a directory that identifies it. followed by a regular expression for the desired path.

Syntax:

Content Access Point/Regular Expression

Example:

Match all requests to a customer origin called myorigin via the following syntax:

/800001/myorigin/(.*)
Multiple Customer Origins: Match against multiple origins by delimiting each desired customer origin using a |.

Syntax:

/80Account Number/(Origin 1|Origin 2|Origin N)/Regular Expression

Example:

Use this pattern to define a capture group that matches a customer origin group called marketing or sales:

/800001/(marketing|sales)/Regular Expression
All Customer Origins: Match against all of your customer origins by specifying .* or (.*).

Syntax:

/80Account Number/(.*)/Regular Expression

Example:

Use this pattern to define a capture group that matches all of your customer origins:

/800001/(.*)/Regular Expression

You may only define a customer origin using a literal value (e.g., marketing) or one of the regular expressions patterns defined above. All other regular expression syntax is disallowed when defining a customer origin. This limitation does not apply to the relative path defined after the content access point.

Destination

Define the URL path to which the above requests will be redirected.

Dynamically construct this URL path using:

A regular expression pattern
HTTP variables

You may not use response metadata (e.g., %{resp_ResponseHeader}) when constructing this path.

It is highly recommended to use an absolute URLThis type of URL identifies a resource (e.g., asset or file) using the following format: scheme://server/path/resource (e.g., http://cdn.mydomain.com/sales/presentation.pdf).. The use of a relative URL may redirect CDN URLs to an invalid path.

URL encoding should not be applied to the specified URL.

Code

Select the response code that will be returned to the requester.

View sample scenario.

In this example, we will demonstrate how to redirect an edge CNAME URL that resolves to this base CDN URL:

http://wpc.0001.edgecastcdn.net/800001/marketing/brochures

Qualifying requests will be redirected to this base edge CNAME URL:

http://cdn.mydomain.com/resources

This URL redirection may be achieved through the following configuration:

Key points:

The URL Redirect feature defines the request URLs that will be redirected. As a result, additional match conditions are not required. Although the match condition was defined as "Always," only requests that point to the "brochures" folder on the "marketing" customer origin will be redirected.

Sample requests:

http://wpc.0001.edgecastcdn.net/800001/marketing/brochures/widgets.pdf

http://wpc.0001.edgecastcdn.net/800001/marketing/brochures/campaignA/final/productC.ppt

http://marketing.mydomain.comThis request will satisfy the URL Redirect's match condition if this hostname points to "/800001/marketing."/brochures/widgets.pdf

http://brochures.mydomain.comThis request will satisfy the URL Redirect's match condition if this hostname points to "/800001/marketing/brochures."/campaignA/final/productC.ppt
All matching requests will be redirected to the edge CNAME URL defined in the Destination option.

Sample scenario #1:

Sample request (CDN URL):

http://wpc.0001.edgecastcdn.net/800001/marketing/brochures/widgets.pdf

Request URL (after redirect):

http://cdn.mydomain.com/resources/widgets.pdf

Sample scenario #2:

Sample request (Edge CNAME URL):

http://marketing.mydomain.comThis hostname points to "/800001/marketing."/brochures/widgets.pdf

Request URL (after redirect):

http://cdn.mydomain.com/resources/widgets.pdf

Sample scenario #3:

Sample request (Edge CNAME URL):

http://brochures.mydomain.comThis hostname points to "/800001/marketing/brochures."/campaignA/final/productC.ppt

Request URL (after redirect):

http://cdn.mydomain.com/resources/campaignA/final/productC.ppt
The Request Scheme (%{scheme}) variable was leveraged in the Destination option. This ensures that the request's scheme remains unchanged after redirection.
The URL segments that were captured from the request are appended to the new URL via "$1."