cos:GetObject, ci:CreateGoodsMattingJob.cos:PutObject.cos:GetObject and cos:PutObject (Note: The resource corresponding to GetObject is the source file, and the resource corresponding to PutObject is the transferred file).GET /<ObjectKey>?ci-process=GoodsMatting HTTP/1.1Host: <BucketName-APPID>.cos.<Region>.myqcloud.comDate: <GMT Date>Authorization: <Auth String>
GET /?ci-process=GoodsMatting&detect-url=<detect-url> HTTP/1.1Host: <BucketName-APPID>.cos.<Region>.myqcloud.comDate: <GMT Date>Authorization: <Auth String>
Parameter | Meaning | Type | Required or Not |
ObjectKey | object filename, for example: folder/document.jpg | String | No |
ci-process | Cloud Infinite processing capability, image matting fixed as GoodsMatting | String | Yes |
detect-url | You can process any publicly accessible image link by filling in detect-url. If detect-url is not specified, the backend will default to processing ObjectKey. If detect-url is filled in, the backend will process the detect-url link, and there is no need to fill in ObjectKey. http://www.example.com/abc.jpg needs to be url encoded, and the processed result is http%25253A%25252F%25252Fwww.example.com%25252Fabc.jpg | String | No |
center-layout | Center display for cutout products; centered display when the value is 1, no processing when the value is 0, default is 0 | Integer | No |
padding-layout | Add padding to all four sides of the processed image in the format padding-layout=<dx>x<dy>, where dx pixels of padding are added to the left and right sides, and dy pixels of padding are added to the top and bottom sides. For example: padding-layout=20x10.Default does not perform blanking operation, maximum value of dx and dy is 1000 pixels | String | No |
HTTP/1.1 200 OKContent-Type: image/pngContent-Length: 98645Date: Tue, 23 Apr 2022 09:06:16 GMTServer: tencent-ciStatus: 200 OKx-cos-request-id: NWFjMzQ0MDZfOTBmYTUwXzZkZV8z****[pic-content]
PUT /<ObjectKey> HTTP/1.1Host: <BucketName-APPID>.cos.<Region>.myqcloud.comDate: GMT DateAuthorization: Auth StringPic-Operations: <PicOperations>
Header Name | Description | Type |
Pic-Operations | Parameters for image operations | String |
Parameter Name | Type | Required or Not | Description |
is_pic_info | Int | No | Whether to return original image information, 0 for no return, 1 for return, default is 0 |
rules | Array | No | Processing rules, one rule corresponds to one processing result (currently supports five rules), leave blank to skip image processing |
Parameter Name | Type | Required or Not | Description |
bucket | String | No | Destination bucket name for storing results, format is BucketName-AppId. If not specified, it defaults to the current bucket. |
fileid | String | Yes | Storage path and name of the processed file. Naming rules description. For example, the source file path and name are: /p1/test1.jpg Absolute path starts with /, for example when the fileid value is /p2/test2.jpg, it means a file named test2.jpg is stored in the p2 folder Relative path does not start with /, for example when the fileid value is p2/test2.jpg, it means a p2 folder is created in the p1 folder, and then a file named test2.jpg is stored in the p2 folder Do not end with /, otherwise an empty filename will occur If you want the repaired image to overwrite the original image, set the fileid field to <ObjectKey> |
rule | String | Yes | Fixed as: ci-process=GoodsMatting, simultaneously support center-layout and padding-layout parameters (see download processing parameter description), parameters are connected with &, for example: ci-process=GoodsMatting¢er-layout=1&padding-layout=20x10 |
Node Name (Keyword) | Parent Node | Description | Type |
UploadResult | None. | Request result. | Container |
Node Name (Keyword) | Parent Node | Description | Type |
OriginalInfo | UploadResult | Image information | Container |
ProcessResults | UploadResult | Request processing result | Container |
Node Name | Parent Node | Description | Type |
Key | OriginalInfo | Original image filename | String |
Location | OriginalInfo | path to the image | String |
Etag | OriginalInfo | ETag value of the original image | String |
Node Name (Keyword) | Parent Node | Description | Type |
Object | ProcessResults | Processing result of each image | Container |
Node Name (Keyword) | Parent Node | Description | Type |
Key | Object | Image file name after image matting | String |
Location | Object | Image link after image matting | String |
ETag | Object | ETag value of the image after image matting | String |
Size | Object | Image size after image matting | Int |
PUT /<ObjectKey> HTTP/1.1Host: <BucketName-APPID>.cos.<Region>.myqcloud.comDate: GMT DateAuthorization: Auth StringPic-Operations:{"is_pic_info": 1,"rules": [{"fileid": "exampleobject","rule": "ci-process=GoodsMatting"}]}
HTTP/1.1 200 OKContent-Type: application/xmlContent-Length: 645Date: Tue, 23 Apr 2022 09:06:16 GMTStatus: 200 OKServer: tencent-cix-cos-request-id: NWFjMzQ0MDZfOTBmYTUwXzZkZV8z****<UploadResult><OriginalInfo><Key>goods_matting.jpg</Key><Location>examplebucket-1250000000.cos.ap-chengdu.myqcloud.com/filename.jpg</Location><ETag>"ed60e3598e6862d8c8443a06acfb2153"</ETag></OriginalInfo><ProcessResults><Object><Key>goods_matting_process.jpeg</Key><Location>examplebucket-1250000000.cos.ap-chengdu.myqcloud.com/exampleobject</Location><Format/><Size>354256</Size><ETag>"521451f63c331becf533e466732c1091"</ETag></Object></ProcessResults></UploadResult>
POST /<ObjectKey>?image_process HTTP/1.1Host: <BucketName-APPID>.cos.<Region>.myqcloud.comDate: GMT DateAuthorization: Auth StringPic-Operations: <PicOperations>
Header Name | Description | Type |
Pic-Operations | Parameters for image operations | String |
Parameter Name | Type | Required or Not | Description |
is_pic_info | Int | No | Whether to return original image information, 0 for no return, 1 for return, default is 0 |
rules | Array | No | Processing rules. One rule corresponds to one processing result (currently supports five rules). If left blank, no image processing will be performed. |
Parameter Name | Type | Required or Not | Description |
bucket | String | No | Destination bucket name for storing results, format is BucketName-AppId. If not specified, it defaults to the current bucket. |
fileid | String | Yes | Storage path and name of the processed file. Naming rules description. For example, the source file path and name are: /p1/test1.jpg Absolute path starts with /, for example when the fileid value is /p2/test2.jpg, it means a file named test2.jpg is stored in the p2 folder Relative path does not start with /, for example when the fileid value is p2/test2.jpg, it means a p2 folder is created in the p1 folder, and then a file named test2.jpg is stored in the p2 folder Do not end with /, otherwise an empty filename will occur If you want the repaired image to replace the original image, set the fileid field to <ObjectKey> |
rule | String | Yes | Fixed as: ci-process=GoodsMatting, simultaneously supports center-layout and padding-layout parameters (see download processing parameter description for details), parameters are connected with &, e.g.: ci-process=GoodsMatting¢er-layout=1&padding-layout=20x10 |
Node Name (Keyword) | Parent Node | Description | Type |
UploadResult | None. | Request result. | Container |
Node Name (Keyword) | Parent Node | Description | Type |
OriginalInfo | UploadResult | Image information | Container |
ProcessResults | UploadResult | Request processing result | Container |
Node Name | Parent Node | Description | Type |
Key | OriginalInfo | Original image filename | String |
Location | OriginalInfo | Path to the original image | String |
Etag | OriginalInfo | ETag value of the original image | String |
Node Name (Keyword) | Parent Node | Description | Type |
Object | ProcessResults | Processing result of each image | Container |
Node Name (Keyword) | Parent Node | Description | Type |
Key | Object | Image file name after image matting | String |
Location | Object | Image link after image matting | String |
ETag | Object | ETag value of the image after image matting | String |
Size | Object | Image size after image matting | Int |
POST /<ObjectKey>?image_process HTTP/1.1Host: <BucketName-APPID>.cos.<Region>.myqcloud.comDate: GMT DateContent-length: SizeAuthorization: Auth StringPic-Operations:{"rules": [{"fileid": "exampleobject","rule": "ci-process=GoodsMatting"}]}
HTTP/1.1 200 OKContent-Type: application/xmlContent-Length: 645Date: Tue, 23 Apr 2022 09:06:16 GMTStatus: 200 OKServer: tencent-cix-cos-request-id: NWFjMzQ0MDZfOTBmYTUwXzZkZV8z****<UploadResult><OriginalInfo><Key>goods_matting.jpg</Key><Location>examplebucket-1250000000.cos.ap-chengdu.myqcloud.com/filename.jpg</Location><ETag>"ed60e3598e6862d8c8443a06acfb2153"</ETag></OriginalInfo><ProcessResults><Object><Key>goods_matting_process.jpeg</Key><Location>examplebucket-1250000000.cos.ap-chengdu.myqcloud.com/exampleobject</Location><Format/><Size>354256</Size><ETag>"521451f63c331becf533e466732c1091"</ETag></Object></ProcessResults></UploadResult>
Feedback