Starting from January 1, 2024, to ensure the security and stability of the overall service, the Cloud Object Storage (COS) service will impose the following restrictions on the use of bucket domain:
For buckets created after January 1, 2024, COS will not support the use of path-style domain.
For buckets created after January 1, 2024, if the COS default domain is used to access objects, previewing of any file type will not be supported, and downloading of apk, ipa file types will not be permitted.
Path-Style Domain Not Supported
For buckets created after January 1, 2024, the use of path-style domain is not supported, only virtual-hosted-style domain is permitted. Existing buckets remain unaffected, however, it is recommended to prioritize the use of virtual-hosted-style domain.
|
path-style | cos.<Region>.myqcloud.com/<BucketName-APPID>
|
virtual-hosted-style | <BucketName-APPID>.cos.<Region>.myqcloud.com
|
Default Domain Do Not Support Preview, APK and IPA File Types Do Not Support Download
For buckets created after January 1, 2024, if users access files using default domain (including default bucket domain, static website domain, and global acceleration domain), any type of file will not support preview but will be directly downloaded. COS will add two headers in the return header:
x-cos-force-download:true
Content-Disposition: attachment
For buckets created after January 1, 2024, if users access apk or ipa type files (with file extensions .apk or .ipa) using the default domain (including the default bucket domain, static website domain, and global acceleration domain), download requests will return an error. An example of the error message is as follows:
HTTP/1.1 400 Bad Request
<?xml version="1.0" encoding="UTF-8"?>
<Error>
<Code>DownloadForbidden</Code>
<Message>The APK/IPA file is not allowed to be distributed in a public network using COS default domain, please use custom domain instead.</Message>
</Error>
If you want to preview files directly through your browser or download apk, ipa type objects stored within the bucket, please access the objects via a custom domain. For more information, see Enabling Custom Origin Server Domains. For buckets created prior to January 1, 2024, the preview and download behavior of the default bucket domain remains unaffected. However, it is recommended that you prioritize the use of a custom domain.
Was this page helpful?