All Documents
Current Document

Content is empty

If you don't find the content you expect, please try another search term


Configure redirection-based back-to-origin (mirroring)

Last updated:2024-03-15 14:07:25

The redirection-based back-to-origin service is used to seamlessly migrate data to KS3. This service is applicable if you need to migrate your service running on your self-built origin servers or other cloud products to KS3 without interrupting the service.

Assume that a KS3 bucket is configured with the redirection-based back-to-origin service. When you send a request to KS3 to access an object that does not exist in the bucket, KS3 returns status code 302 with a URL pointing to the origin server in the header field Location. At the same time, KS3 asynchronously requests the object from the origin server and saves it to the bucket.


  • You can use the redirection-based back-to-origin service to migrate an object of up to 50 GB in size.

  • When you send a request to KS3 to access an object that does not exist in KS3, KS3 asynchronously downloads the object from the origin server and saves it to KS3. However, KS3 does not ensure the efficiency and success rate of this action.

  • You can configure multiple origin servers for a bucket. In this case, separate origin servers with semicolons (; ). When you send a request to KS3 to access an object that does not exist in KS3, KS3 attempts to pull the object from the origin servers in order as configured. When KS3 obtains the object from an origin server, it no longer requests the object from the remaining origin servers.

  • You can set the origin address to a domain name or an IP address. Multiple origin addresses must be separated with semicolons (; ). The origin address must be 1 to 512 characters in length.


  1. Log in to the KS3 console and click Bucket in the left navigation pane. On the Bucket list page, click the name of the target bucket. On the page that appears, click Bucket Settings. Click the Mirror tab. On the Mirror tab, click Add Rule.

After origin servers are configured, resources on the origin servers are automatically and smoothly migrated to the current KS3 bucket. To access these resources, use an access URL in the following format:https://{Bucket name}{Resource path} . Note that KS3 buckets cannot be used as origin servers. By default, data of origin servers is synchronized to the specified bucket.

After an origin server is configured and the data is migrated, the origin server may be blocked by the search engine because the content of the origin server is almost the same as that of the corresponding bucket. To resolve this issue, configure the search engine profile robots.txt.

  1. Configure access control.

    You can set the objects uploaded to the current bucket to be public or private.

  2. Configure object pre-pushing.

Note: You can configure object pre-pushing only after the redirection-based back-to-origin service is configured.

You can pull objects from origin servers to KS3 based on the resource list in the template provided by KS3, and store the objects based on the set rules.


  • You can pre-push up to 100,000 objects at a time. For additional objects, pre-push them again.

  • The pre-pushing result is saved in the Object pre-pushing result file of the corresponding bucket. It takes some time to pre-push objects. Wait for a while before you view the pre-pushing result.

  • Specify the objects to be pre-pushed in the format specified in the template.

On this page
Pure ModeNormal Mode

Pure Mode

Click to preview the document content in full screen