Dear Tencent Cloud User,
To further improve platform content security and compliance, and to prevent the origin-pull feature from being abused for illegal content distribution or malicious traffic diversion, Cloud Object Storage (COS) will make the following changes to the origin-pull feature, effective December 1, 2026 (UTC+8):
1. Redirect origin-pull is discontinued: starting December 1, configuring redirect origin-pull rules will no longer be supported.
2. Synchronous and asynchronous origin-pull can no longer disable "Follow 3xx Redirects": starting December 1, when configuring synchronous or asynchronous origin-pull, the "Follow 3xx Redirects" parameter (FollowRedirection) can no longer be disabled.
Impact
|
Rules that exist before December 1, 2026 | Not affected by this change. |
Rules added or modified on or after December 1, 2026 | Redirect origin-pull rules can no longer be configured. When configuring synchronous or asynchronous origin-pull rules, "Follow 3xx Redirects" can no longer be disabled. |
Recommendations
1. Assess your current workloads: check whether any of your workloads depend on redirect origin-pull, or on the behavior of "not following redirects and passing the origin's 3xx response through to the client".
2. Adjust your origin-pull approach: for scenarios that rely on redirect origin-pull for a bucket, switch to synchronous or asynchronous origin-pull, and keep "Follow 3xx Redirects" enabled.
Compliance Statement
COS will continue to conduct compliance inspections on the origin-pull feature. If a bucket is found to engage in abusive behavior such as illegal redirection or malicious traffic diversion, COS reserves the right to restrict or disable its origin-pull capability in accordance with the applicable agreements.
If you have any questions, please contact us by submitting a ticket. Thank you for your understanding and support.