Checking Whether an Object Exists
Function
This API is used to check whether an object exists. If the returned HTTP status code is 200, the object exists. If the returned HTTP status code is 404, the object or bucket does not exist.
Restrictions
- To check whether an object exists, you must be the bucket owner or have the required permission (obs:object:GetObject in IAM or GetObject in a bucket policy). For details, see Introduction to OBS Access Control, IAM Custom Policies, and Configuring an Object Policy.
- The mapping between OBS regions and endpoints must comply with what is listed in Regions and Endpoints.
Method
obsClient.doesObjectExist(final GetObjectMetadataRequest request)
Request Parameters
| Parameter | Type | Mandatory (Yes/No) | Description |
|---|---|---|---|
| request | Yes | Explanation: Request parameters. For details, see Table 2. |
| Parameter | Type | Mandatory (Yes/No) | Description |
|---|---|---|---|
| bucketName | String | Yes | Explanation: Bucket name. Restrictions:
Default value: None |
| objectKey | String | Yes | Explanation: Object name. An object is uniquely identified by an object name in a bucket. An object name is a complete path that does not contain the bucket name. For example, if the address for accessing the object is examplebucket.obs.ap-southeast-1.myhuaweicloud.com/folder/test.txt, the object name is folder/test.txt. Value range: The value must contain 1 to 1,024 characters. Default value: None |
| versionId | String | No | Explanation: Object version ID. Value range: The value must contain 32 characters. Default value: None |
| userHeaders | HashMap<String, String> | No | Explanation: User header list. In HashMap, the String key and value indicate the name and value of the user header field respectively. The SDK does not process the userHeaders and instead transparently transmits it to the server for later use. Value range: The value must contain 32 characters. Default value: None |
| encodeHeaders | boolean | No | Explanation: Whether to encode and decode HTTP headers. Value range: true: HTTP headers are encoded and decoded. false: HTTP headers are not encoded or decoded. Default value: true |
| sseHeader | No | Explanation: Server-side decryption header. For details, see Table 3. |
| Parameter | Type | Mandatory (Yes/No) | Description |
|---|---|---|---|
| algorithm | Yes | Explanation: SSE-C is used for encrypting objects on the server side. Value range: AES256, indicating AES is used to encrypt the object in SSE-C. For details, see Table 4. Default value: None | |
| sseAlgorithm | No | Explanation: Encryption algorithm. Restrictions: Only AES256 is supported. Value range: See Table 5. Default value: None | |
| sseCKey | byte[] | Yes | Explanation: Key used for encrypting the object when SSE-C is used, in byte[] format. Default value: None |
| sseCKeyBase64 | String | No | Explanation: Base64-encoded key used for encrypting the object when SSE-C is used. Default value: None |
Responses
| Method | Return Value Type | Description |
|---|---|---|
| doesObjectExist(final GetObjectMetadataRequest request) | boolean | Whether the object exists in the bucket. |
Sample Code
The following code shows how to check whether object objectname exists in bucket examplebucket.
import android.util.Log;
import com.obs.services.ObsClient;
import com.obs.services.exception.ObsException;
import com.obs.services.model.GetObjectMetadataRequest;
public class DoesObjectExistDemo {
private static final String TAG = "DoesObjectExistDemo";
public void doesObjectExist() {
// Hard-coded or plaintext AK and SK are risky. For security purposes, encrypt your AK and SK and store them in the configuration file or environment variables. In this example, the AK and SK are stored in environment variables for identity authentication. Before running the code in this example, configure environment variables ACCESS_KEY_ID and SECRET_ACCESS_KEY_ID.
// Obtain an AK/SK pair on the management console.
String ak = System.getenv("ACCESS_KEY_ID");
String sk = System.getenv("SECRET_ACCESS_KEY_ID");
// Enter the endpoint corresponding to the bucket. CN North-Beijing4 is used here as an example. Replace it with the one currently in use.
String endPoint = "https://your-endpoint";
// Create an ObsClient instance.
ObsClient obsClient = new ObsClient(ak, sk, endPoint);
try {
// Check whether the specified object exists.
boolean exists = obsClient.doesObjectExist("examplebucket", "objectname");
Log.i(TAG, exists ? "object exists!" : "object does not exist!");
Log.i(TAG, "doesObjectExist successfully");
// Alternatively, use the GetObjectMetadataRequest method.
GetObjectMetadataRequest request = new GetObjectMetadataRequest("examplebucket", "objectname");
boolean exists2 = obsClient.doesObjectExist(request);
Log.i(TAG, exists2 ? "object exists!" : "object does not exist!");
} catch (ObsException e) {
Log.e(TAG, "doesObjectExist failed");
// Request failed. Print the HTTP status code.
Log.e(TAG, "HTTP Code:" + e.getResponseCode());
// Request failed. Print the server-side error code.
Log.e(TAG, "Error Code:" + e.getErrorCode());
// Request failed. Print the error details.
Log.e(TAG, "Error Message:" + e.getErrorMessage());
// Request failed. Print the request ID.
Log.e(TAG, "Request ID:" + e.getErrorRequestId());
Log.e(TAG, "Host ID:" + e.getErrorHostId());
} catch (Exception e) {
Log.e(TAG, "doesObjectExist failed");
// Print other error information.
Log.e(TAG, e.getMessage());
}
}
} What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot