edit-icon download-icon

Set back-to-origin rules

Last Updated: Feb 11, 2018

You can set back-to-origin rules to define whether to retrieve origin data by mirroring or redirection. Back-to-origin rules are usually used for hot migration of data and redirection of specific requests. You can configure up to five back-to-origin rules, which is executed by the system in sequence.

Note: Back-to-origin does not support intranet endpoint. For more information on traffic fees, see Pricing.

Procedure

  1. Log on to the OSS console.

  2. Click to open the target bucket.

  3. Click the Basic Settings tab.

    basic settings

  4. In the Back-to-Origin area, click Edit.

  5. Click Create Rule.

  6. In the Back-to-Origin Type area, select Mirroring or Redirect.

    • When Mirroring is configured, if a requested file is not found on OSS, it is automatically retrieved from the source site, saved to the OSS, and the content is returned to the user.

    • When Redirect is configured, the requests that meet the response condition are returned to the redirected URL through HTTP redirection. A browser or client then obtains the content from the source site.

  7. Click OK to save the rule.

Note: After the rule is successfully saved, you can view the configured rule in the rule list and perform corresponding Edit or Clear operations.

Thank you! We've received your feedback.