This document describes the common response headers that may be used in API requests. The headers mentioned below will not be detailed again in specific API documents.
|Content-Length||HTTP response length in bytes as defined in RFC 2616||string|
|Content-Type||HTTP response content type (MIME) as defined in RFC 2616.||string|
|Connection||Indicates whether the network connection will be closed after completion of the response as defined in RFC 2616. Enumerated values: `keep-alive`, `close`.||Enum|
|Date||Server response time in GMT format as defined in RFC 1123, such as
|Etag||An entity tag (ETag) is an information tag that identifies the content of an object when it is created, such as
|Server||Name of the server that accepts the request and returns the response. Default value:
|x-cos-request-id||An ID automatically generated by the server for each request when the request is sent.||string|
|x-cos-trace-id||An ID automatically generated by the server for each error when requests fail. This header will be included in the response only if a request fails.||string|
For APIs that support server-side encryption (SSE) and use SSE in the request, the following response headers will be returned according to the specific encryption method. For more information, see Server-side Encryption Overview.
|x-cos-server-side-encryption||If an object is uploaded with SSE-COS or an SSE-COS-encrypted object is downloaded, the response of the request will return this header, indicating the server-side encryption algorithm used when the object is uploaded.||string|
|x-cos-server-side-encryption-customer-algorithm||If an object is uploaded with SSE-C or an SSE-C-encrypted object is downloaded, the response of the request will return this header, indicating the server-side encryption algorithm used when the object is uploaded.||string|
|x-cos-server-side-encryption-customer-key-MD5||Base64-encoded MD5 hash of the server-side encryption key used during object upload.