tencent cloud

APIs

DocumentaçãoAPIsCloud Object StorageCommon Response Headers

Common Response Headers

Download
Modo Foco
Tamanho da Fonte
Última atualização: 2026-05-19 15:46:09

Description

This document describes the common Response headers that appear when you use the API. The headers mentioned here are not repeated in subsequent specific API documentation.

Response Headers

Header Name
Description
Type
Content-Length
The length (in bytes) of the HTTP response content as defined in RFC 2616.
string
Content-Type
The content type (MIME) of the HTTP response as defined in RFC 2616.
string
Connection
Defined in RFC 2616, it indicates whether to close the network connection after the response is completed. Enumeration values: keep-alive, close.
enum
Date
The server response time in GMT format as defined in RFC 1123, for example, Wed, 29 May 2019 04:10:12 GMT.
string
ETag
ETag, short for Entity Tag, is an informational tag that identifies the content of an object when it is created and can be used to check whether the object's content has changed. Its format is "<etag_value>", enclosed in double quotes with an ASCII string in between, for example, "8e0b617ca298a564c3331da28dcb50df". This header does not necessarily return the MD5 value of the object; it varies depending on the object's upload and encryption methods. If you need to verify the consistency between a file uploaded to the cloud and the local file, we recommend using the CRC64 code in the x-cos-hash-crc64ecma header for verification.
string
Last-Modified
The time of the object's most recent upload, for example, Fri, 10 Apr 2020 18:17:25 GMT.
string
Server
The name of the server that receives requests and returns responses. Default value: tencent-cos.
string
Transfer-Encoding
The transfer encoding format as defined in RFC 2616.
string
x-cos-hash-crc64ecma
The CRC64 value of the object. For details, see the CRC64 Verification document.
integer
x-cos-request-id
The server automatically generates an ID for each request when it is sent.
string
x-cos-trace-id
When a request fails, the server automatically generates an ID for the error. This header is included in the response only when a request fails.
string


Special Headers for SSE

For APIs that support Server Side Encryption (SSE) and use SSE in requests, response headers described in the following are returned based on the specific encryption type. For details, see Server-side Encryption Overview.

SSE-COS

Header Name
Description
Type
x-cos-server-side-encryption
When SSE-COS is used during object upload or objects encrypted with SSE-COS are downloaded, responses to the request carry this header, indicating that the SSE algorithm is used during object upload.
string


SSE-KMS

Header Name
Description
Type
x-cos-server-side-encryption
When SSE-KMS is used during object upload or objects encrypted with SSE-KMS are downloaded, responses to the request carry this header, indicating that the SSE algorithm is used during object upload.
string
x-cos-server-side-encryption-cos-kms-key-id
The customer master key (CMK) of the Key Management Service (KMS) is returned. If it is not specified, the CMK created by COS by default is returned.
string

SSE-C

Header Name
Description
Type
x-cos-server-side-encryption-customer-algorithm
When SSE-C is used during object upload or objects encrypted with SSE-C are downloaded, responses to the request carry this header, indicating that the SSE algorithm is used during object upload.
string
x-cos-server-side-encryption-customer-key-MD5
Base64-encoded MD5 hash value of the SSE key used during object upload.
For example, U5L61r7jcwdNvT7frmUG8g==.
string

Anterior: Common Request HeadersPróximo: Error Codes

Ajuda e Suporte

Esta página foi útil?

comentários