Feature Overview

Assume that a resource on the customer's origin server is moved to a different URL and the URL of the resource that is cached on the CDN points of presence (POPs) is updated. However, a client requests the resource from the original URL. In this case, CDN POPs must rewrite the URL to redirect the request to the new URL. For example, a video-on-demand (VOD) file is moved from the /stream/ directory to the /vod/ directory. The technical implementation is as follows: The CDN POP returns the 302 response status code for a redirect, enabling the client to obtain the changed URL from the Location header and resend an access request to the CDN POP. This ensures that the user can obtain the correct file.

Additional Considerations

For this feature to take effect, clients must support redirection.

Procedure

Currently, this feature cannot be configured on your own. If you need to configure this feature,please contact our customer support team via hotline (852)31000000 or email global.noc@chinatelecomglobal.com. This feature can only be manually configured by the technical support team.

Please provide the following information:

Parameter	Description
Status Code	Available status 301, 302, 303, 307, and 308.
Path to be rewritten	Enter a path that starts with a forward slash (/). The path cannot contain http:// or domain names. You can use Perl Compatible Regular Expressions (PCRE) to specify the path, such as ^/qpdxv/(.*).
Target Path	Enter a path that starts with://. The protocol scheme can be http or https. You can use PCRE to specify the target path. For example, $1 and $2 are often used to capture the strings that are enclosed in parentheses within the path to be rewritten. For example, you can specify $scheme://www.example.com/videos/$1 as the target path.

Content Delivery Network

Customized redirection