Feature Overview
Cloud Infinite provides progressive display function for JPG images through the imageMogr2 API.
Authorization Guide
When used with a sub-account, the cos:GetObject permission must be granted. For details, please refer to Cloud Object Storage. For other CI permissions, please refer to Cloud Infinite. Service Activation
Using this feature will activate Cloud Infinite for you by default and bind a bucket. No role authorization is required, it can be used directly.
Use Limits
Only JPG format images are supported. Non-JPG format images can be converted to JPG using image conversion before performing this operation.
Fee Description
This API is a paid service. The incurred fees will be collected by Cloud Infinite. For detailed billing information, see Image Processing Fees. If processing during download is adopted and the download is performed via the public network, the API call will incur Traffic Fees. API Example
GET /<ObjectKey>?imageMogr2/interlace/<Mode> HTTP/1.1
Host: <BucketName-APPID>.cos.<Region>.myqcloud.com
Date: <GMT Date>
Authorization: <Auth String>
Processing Parameter Description
|
ObjectKey | Object filename, for example folder/sample.gif. | String | Yes |
/interlace/ | Output in progressive JPG format. Mode can be 0 or 1. 0: Means disable progressive display; 1: Means enable progressive display. This parameter is valid only when the output image format is JPG. If a non-jpg image format is output, this parameter will be ignored. Default value: 0. | Int | Yes |
/ignore-error/1 | When processing requests carry this parameter, if operations fail due to oversized files or parameter exceeds limit, it will directly return the original image without reporting an error. | String | No |
Practical Example
Save the image with original PNG format as JPG format and set it to progressive display:
http://examples-125xxxxxx.cos.ap-shanghai.myqcloud.com/sample.png?imageMogr2/format/jpg/interlace/1
Important Notes
To prevent unauthorized personnel from accessing and downloading the original image through links that do not carry processing parameters, you can include the processing parameters in the request signature. The processing parameters are the key in the overall parameters, with an empty value. A simple example is provided below (for reference only; the link may be expired and inaccessible). For detailed calculation methods, please refer to Request Signature. http://examples-1251000004.cos.ap-shanghai.myqcloud.com/sample.jpeg?q-sign-algorithm=sha1&q-ak=**********************************&q-sign-time=1593342360;1593342720&q-key-time=1593342360;1593342720&q-header-list=&q-url-param-list=watermark%252f1%252fimage%252fahr0cdovl2v4yw1wbgvzlteyntewmdawmdqucgljc2gubxlxy2xvdwquy29tl3nodwl5aw4uanbn%252fgravity%252fsoutheast&q-signature=**************************************&watermark/1/image/aHR0cDovL2V4YW1wbGVzLTEyNTEwMDAwMDQucGljc2gubXlxY2xvdWQuY29tL3NodWl5aW4uanBn/gravity/southeast