URL Rewrite

Category: URL

Purpose: Rewrites the request URL.

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

Key information:

• The configuration of this feature requires setting the following options:

  Option	Description
  Source	Identify requests that will be rewritten 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 relative path to which the above requests will be rewritten. This relative path, which starts directly after the hostname in the CDN URL, is shown in blue font in the following sample CDN URL. http://wpc.0001.edgecastcdn.net/800001/CustomerOrigin/Path/file.ext Use HTTP variables to dynamically construct this relative path. However, you may not use response metadata (e.g., %{resp_ResponseHeader}). Valid syntax varies according to number of origins being matched in the Source option. Specific Origin: Specify the 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. that identifies the desired origin followed by a regular expression for the desired path. Syntax: Content Access Point/Regular Expression Example: Use a backreference (i.e., $1) to include text captured from the source. /800001/mycustomerorigin/new-path/$1 All or Multiple Customer Origins: If the Source option matches all or multiple customer origins using a capture group, then you may use a backreference (i.e., $1) to reinsert the name of the customer origin into the URL. Syntax: /80Account Number/$1/Regular Expression Example: Use this pattern to ensure that requests point to the same customer origin: /800001/$1/Regular Expression You may define a customer origin using either a literal value (e.g., marketing) or a backreference. 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.

• This feature allows our edge servers to rewrite the URL without performing a traditional redirect. This means that the requester will receive the same response code as if the rewritten URL had been requested.

• This feature takes precedence when multiple features will be applied to a request.

  Learn more.

Compatibility

This feature includes matching criteria that must be met before it can be applied to a request. In order to prevent setting up conflicting match criteria, this feature is incompatible with the following match conditions:

• AS Number
• CDN Origin
• Client IP Address
• Customer Origin
• Request Scheme
• URL Path Literal
• URL Path Regex
• URL Path Wildcard
• URL Path Directory Literal
• URL Path Directory Wildcard
• URL Path Extension Literal
• URL Path Extension Wildcard
• URL Path Filename Literal
• URL Path Filename Wildcard
• URL Query Literal
• URL Query Regex
• URL Query Wildcard
• URL Query Parameter Literal
• URL Query Parameter Wildcard

Edgecast CDN