tencent cloud

Cloud Object Storage

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Features
Use Cases
Strengths
Concepts
Regions and Access Endpoints
Specifications and Limits
Service Regions and Service Providers
Billing
Billing Overview
Billing Method
Billable Items
Free Tier
Billing Examples
Viewing and Downloading Bill
Payment Overdue
FAQs
Getting Started
Console
Getting Started with COSBrowser
User Guide
Creating Request
Bucket
Object
Data Management
Batch Operation
Global Acceleration
Monitoring and Alarms
Operations Center
Data Processing
Content Moderation
Smart Toolbox
Data Processing Workflow
Application Integration
User Tools
Tool Overview
Installation and Configuration of Environment
COSBrowser
COSCLI (Beta)
COSCMD
COS Migration
FTP Server
Hadoop
COSDistCp
HDFS TO COS
GooseFS-Lite
Online Tools
Diagnostic Tool
Use Cases
Overview
Access Control and Permission Management
Performance Optimization
Accessing COS with AWS S3 SDK
Data Disaster Recovery and Backup
Domain Name Management Practice
Image Processing
Audio/Video Practices
Workflow
Direct Data Upload
Content Moderation
Data Security
Data Verification
Big Data Practice
COS Cost Optimization Solutions
Using COS in the Third-party Applications
Migration Guide
Migrating Local Data to COS
Migrating Data from Third-Party Cloud Storage Service to COS
Migrating Data from URL to COS
Migrating Data Within COS
Migrating Data Between HDFS and COS
Data Lake Storage
Cloud Native Datalake Storage
Metadata Accelerator
GooseFS
Data Processing
Data Processing Overview
Image Processing
Media Processing
Content Moderation
File Processing Service
File Preview
Troubleshooting
Obtaining RequestId
Slow Upload over Public Network
403 Error for COS Access
Resource Access Error
POST Object Common Exceptions
API Documentation
Introduction
Common Request Headers
Common Response Headers
Error Codes
Request Signature
Action List
Service APIs
Bucket APIs
Object APIs
Batch Operation APIs
Data Processing APIs
Job and Workflow
Content Moderation APIs
Cloud Antivirus API
SDK Documentation
SDK Overview
Preparations
Android SDK
C SDK
C++ SDK
.NET(C#) SDK
Flutter SDK
Go SDK
iOS SDK
Java SDK
JavaScript SDK
Node.js SDK
PHP SDK
Python SDK
React Native SDK
Mini Program SDK
Error Codes
Harmony SDK
Endpoint SDK Quality Optimization
Security and Compliance
Data Disaster Recovery
Data Security
Cloud Access Management
FAQs
Popular Questions
General
Billing
Domain Name Compliance Issues
Bucket Configuration
Domain Names and CDN
Object Operations
Logging and Monitoring
Permission Management
Data Processing
Data Security
Pre-signed URL Issues
SDKs
Tools
APIs
Agreements
Service Level Agreement
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary
DocumentaçãoCloud Object StorageAPI DocumentationData Processing APIsImage ProcessingSmart Image CompressionQuerying Smart Compression Status

Querying Smart Compression Status

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2026-01-09 14:35:45

Feature Description

This API is used to query the status of the intelligent image compression feature.

Authorization Description

When used by a sub-account, the ci:DescribeImageSlim permission is required. For details, please refer to Cloud Infinite.

Service Activation

To use this feature, you need to enable Cloud Infinite in advance and bind a bucket. For details, see Binding a Bucket.

Use Limits

When using this API, please first confirm the relevant restrictions. For details, see Specifications and Limits.

Request

Request sample

GET /?image-slim HTTP/1.1
Host: <BucketName-APPID>.pic.<Region>.myqcloud.com 
Date: <GMT Date>
Authorization: <Auth String>
Note:
Authorization: Auth String. For details, see Request Signature document.

Request header

This request operation only uses common request headers. To learn about common request headers, see Common Request Headers.

Request body

The request does not have a request body.

Response

Response Headers

This response uses only common response headers. To learn about common response headers, see Common Response Headers.

Response Body

<?xml version="1.0" encoding="UTF-8" ?>
<ImageSlim>
    <Status>off</Status>
    <SlimMode>API</SimMode>
    <Suffixs>
        <Suffix>jpg</Suffix>
        <Suffix>png</Suffix>
    </Suffixs>
</ImageSlim>

Parameter Description

Node Name (Keyword)
Parent Node
Description
Status
ImageSlim
State of smart compression, including values:
on: Smart compression is enabled
off: Smart compression is disabled.
SlimMode
ImageSlim
Usage modes of smart compression. There are two kinds:
API: The usage method for enabling smart compression. Once activated, images can be compressed using intelligent compression parameters during image download.
Auto: The automatic usage method for enabling smart compression. Once activated, no parameters are needed, and images in the specified format within the bucket will be automatically compressed by smart compression when accessed.
Suffixs
ImageSlim
Returned when the value of SlimMode contains Auto, indicating the need to automatically perform compression on the image format.
Suffix
Suffixs
Image formats for automatic compression, including values: jpg, png, gif.
The API supports JSON format return. When the request header specifies accept=application/json, the response body is as follows:
{
    "ImageSlim":{
        "Status":"on",
        "SlimMode":"Auto",
        "Suffixs":{
            "Suffix":[
                "jpg"
                "png"
            ]
        }
    }
}

Anterior: Enabling Smart CompressionPróximo: Disabling Smart Compression

Ajuda e Suporte

Esta página foi útil?

comentários