GET Object

Description

You can call this operation to obtain objects from Kingsoft Cloud Standard Storage Service (KS3). To call this operation, you must have the read permissions on the object. If you grant read permissions to the anonymous user, no signature is required in this operation. To generate a download link, see Send signatures by using URL query strings.

A KS3 bucket does not have a directory hierarchy, as you can find in a typical computer file system. However, you can set the value that implies a folder structure to the object key to achieve a logical hierarchy. For example, you can name an object photos/2006/February/sample.jpg instead of sample.jpg.

In this operation, you can specify the full name of an object to obtain an object with a logical hierarchy. Assume that an object named photos/2006/February/sample.jpg is placed in a bucket named as examplebucket. In this case, the logical resource name can be /examplebucket/photos/2006/February/sample.jpg.

Permission

To call this operation, you must have the read permissions on the object. If the requested object does not exist, KS3 responds based on whether you have the read permissions.

• If you have the read permissions on the bucket, KS3 returns an HTTP 404 error with the error message "no such key."
• If you do not have the read permissions on the bucket, KS3 returns an HTTP 403 error with the error message "access denied."

Request

Request syntax

GET /{ObjectKey} HTTP/1.1
Host: {BucketName}.{endpoint}
Date: {date}
Authorization: {SignatureValue}
Range:bytes=byte_range

References:

• Endpoints and regions
• Request signature

Request parameters

Assume that you require a specific response header, for example, Content-Disposition to be returned in the GET response. You need to set the response header in the GET request.

You can set response headers by using the request parameters listed in the table below. The headers take effect only when KS3 returns HTTP status code 200. You can set Content-Type, Content-Language, Expires, Cache-Control, Content-Disposition, and Content-Encoding to be returned by using the following parameters.

Request headers

This operation supports all common request headers and the request headers that are described in the following table. For more information, see Common request headers.

Request

No request body is used.

Response

Response headers

Response body

No response body is returned.

Operation-specific errors

This operation does not return operation-specific errors.

Examples

Sample request

GET /my-image.jpg HTTP/1.1
Host: ks3-example.ks3-cn-beijing.ksyuncs.com
Date: Fri, 26 Dec 2014 06:48:45 GMT
Authorization: authorization string

Sample response

HTTP/1.1 200 OK
x-kss-request-id: 5a868ca0ebd74bcc8eff1f1a7c9bcd6c
Date: Fri, 26 Dec 2014 06:48:46 GMT
Last-Modified: Wed, 12 Oct 2009 17:50:00 GMT
ETag: "798308f9638ea5b28d5f25e4d677ffac"
Content-Length: 434234
Content-Type: text/plain
Connection: close
Server: Tengine
Content-MD5:eYMI+WOOpbKNXyXk1nf/rA==
[434234 bytes of object data]

Notes:

1. If an object is uploaded to KS3 in multiple parts, the Content_MD5 header will not be returned when you call the GET operation.

2. If an object is uploaded to KS3 through PUT or POST, the Content_MD5 header will be returned when you call the GET operation.

Usage notes

• The setting of request parameters takes effect only when KS3 returns HTTP status code 200.
• The value of Range must be in the correct format; otherwise, KS3 will return HTTP status code 416.
• The x‑kss‑tagging‑count header is returned only if you have the ks3:GetObjectTagging permission on tags. If you have the ks3:GetObject permission but not the ks3:GetObjectTagging permission, the x-kss-tagging-count header will not be returned.
• For more information about how to download a private file by using a browser, see Send signatures by using URL query strings.