Below are precautions for using a global acceleration domain name:
For more information on global acceleration, see Overview.
/files/v2/appid/bucketname/
?Global acceleration is a feature of COS V5 but /files/v2/
is a reserved field of COS V4. Using the reserved field in COS V5 will cause an internal logic conflict. Be sure to use a V5 API to access the global acceleration domain name. For more information, please see API Overview.
Currently, global acceleration domain names support file upload and download. Related APIs are APIs that support acceleration domain names as listed below.
No. | API | No. | API |
---|---|---|---|
1 | PutObject | 7 | ListParts |
2 | PostObject | 8 | UploadPart |
3 | GetObject | 9 | AbortMultipartUpload |
4 | HeadObject | 10 | CompleteMultipartUpload |
5 | OptionsObject | 11 | ListMultipartUploads |
6 | InitiateMultipartUpload | - | - |
After global acceleration is enabled, global acceleration traffic will be charged only when a Direct Connect linkage between two Tencent Cloud data centers is used for data transmission, which accelerates the data transmission. For example, if data is uploaded from Tibet to the bucket in Beijing, the Tibet data center will connect to the Chengdu data center first and transmit the data to the storage layer in Beijing through the Direct Connect linkage. In such a case, acceleration fees will be charged. If data is uploaded from Tibet to the bucket in Chengdu, the Tibet data center will directly connect to the Chengdu data center. In this case, the data directly falls on the Chengdu layer, there is no acceleration effect, and there will be no extra charge.
Was this page helpful?