Redirection-based back-to-origin

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 the redirection-based back-to-origin service is configured for a KS3 bucket. If a client requests an object that does not exist in the bucket, KS3 returns the 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.

Notes:

• You can use the redirection-based back-to-origin service to migrate an object of up to 50 GB in size.
• If a client requests 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 the origin servers with semicolons (;). When back-to-origin is triggered for an object, KS3 attempts to pull the object from the origin servers in order as configured. If KS3 obtains the object from an origin server, KS3 no longer requests the object from the remaining origin servers.
• If an origin server returns a 301 redirect request that points to another origin server, KS3 does not follow the 301 redirect request to asynchronously pull objects from the eventual origin server. However, KS3 follows 302 redirect requests to pull objects from the eventual origin server.
• 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.

Configure object pre-pushing

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.

Notes:

• You can configure object pre-pushing only after the redirection-based back-to-origin service is configured. The object pre-pushing service does not support Archive buckets.
• If the object name customization and object pre-pushing features are enabled at the same time, the object name customization feature does not take effect on the pre-pushed objects.

For more information about how to configure redirection-based back-to-origin in the KS3 console, see Configure redirection-based back-to-origin.

Note: If an origin server returns a 301 redirect request that points to another origin server, KS3 does not follow the 301 redirect request to asynchronously pull objects from the eventual origin server. However, KS3 follows 302 redirect requests to pull objects from the eventual origin server.