Access-Control-Expose-Headers
diff --git a/docs/obs/api-ref/obs_04_0026.html b/docs/obs/api-ref/obs_04_0026.html
index e286c556..cf1a44bb 100644
--- a/docs/obs/api-ref/obs_04_0026.html
+++ b/docs/obs/api-ref/obs_04_0026.html
@@ -66,6 +66,10 @@
Deleting the Encryption Configuration of a Bucket
+Configuring the Requester-Pays Function for a Bucket
+
+Obtaining the Requester-Pays Configuration Information of a Bucket
+
diff --git a/docs/obs/api-ref/obs_04_0030.html b/docs/obs/api-ref/obs_04_0030.html
index 22c389ee..3a24994f 100644
--- a/docs/obs/api-ref/obs_04_0030.html
+++ b/docs/obs/api-ref/obs_04_0030.html
@@ -64,7 +64,7 @@ Content-Length: length
x-obs-acl
|
Uses the canned ACL for a bucket.
-Value options: private | public-read | public-read-write | public-read-delivered | public-read-write-delivered
+Value options: private, public-read, public-read-write, public-read-delivered, public-read-write-delivered
Type: string
|
No
@@ -137,7 +137,7 @@ Content-Length: length
| Permission
|
Permissions to be granted.
-Value options: READ | READ_ACP | WRITE | WRITE_ACP | FULL_CONTROL
+Value options: READ, READ_ACP, WRITE, WRITE_ACP, FULL_CONTROL
Type: string
|
No
diff --git a/docs/obs/api-ref/obs_04_0032.html b/docs/obs/api-ref/obs_04_0032.html
index a7f6bc4a..d7e93683 100644
--- a/docs/obs/api-ref/obs_04_0032.html
+++ b/docs/obs/api-ref/obs_04_0032.html
@@ -129,7 +129,7 @@ Authorization: signatureValue
|
Permissions of the grantee to the generated logs.
Type: string
-Value options: FULL_CONTROL | READ | WRITE
+Value options: FULL_CONTROL, READ, WRITE
|
No
|
@@ -222,6 +222,7 @@ Authorization: signatureValue
787f2f92b20943998a4fe2ab75eb09b8
|
ID of the requester
+- When an account initiates a request, this parameter value is the account ID. When an IAM user initiates a request, this parameter value is the ID of the account where the IAM user belongs.
- When an anonymous user initiates a request, this parameter value is Anonymous.
|
RequestID
diff --git a/docs/obs/api-ref/obs_04_0033.html b/docs/obs/api-ref/obs_04_0033.html
index 4bf21377..5a86919f 100644
--- a/docs/obs/api-ref/obs_04_0033.html
+++ b/docs/obs/api-ref/obs_04_0033.html
@@ -116,7 +116,7 @@ Content-Length: length
|
Logging permission granted to the grantee for a bucket. The bucket owner is automatically granted the FULL_CONTROL permission when creating the bucket. Logging permissions control access to different logs.
Type: string
-Value options: FULL_CONTROL | READ | WRITE
+Value options: FULL_CONTROL, READ, WRITE
|
TargetBucket
diff --git a/docs/obs/api-ref/obs_04_0034.html b/docs/obs/api-ref/obs_04_0034.html
index 4d0425b6..7b007a30 100644
--- a/docs/obs/api-ref/obs_04_0034.html
+++ b/docs/obs/api-ref/obs_04_0034.html
@@ -4,7 +4,7 @@
FunctionsThis operation configures lifecycle rules that can delete or migrate objects from a bucket at a specified time. Typical application scenarios:
- Delete periodically uploaded files. Some files uploaded periodically need only to be retained for only one week or one month.
- Delete files that are frequently accessed within a certain period of time but are seldom accessed afterward. You can archive these files and then schedule the time for deletion.
- The minimum time for the transition of the bucket storage to Warm or to Cold can be configured. The value ranges from 24 to 8640.
You can perform this operation to create or update the lifecycle configuration of a bucket.
-  - Expired objects deleted based on a lifecycle rule cannot be recovered.
+ - Expired objects deleted based on a lifecycle rule cannot be recovered.
To perform this operation, you must have the PutLifecycleConfiguration permission. By default, only the bucket owner can perform this operation. The bucket owner can grant the permission to other users by configuring the bucket policy or user policy.
The lifecycle configuration enables OBS to delete objects and transition object storage classes at a scheduled time. To prevent a user from doing so, the following permissions granted to the user must be revoked:
@@ -118,12 +118,12 @@ Content-MD5: MD5
Request ElementsIn this request, you need to specify the lifecycle configuration in the request body. The lifecycle configuration can be uploaded in the form of an XML file with elements described in Table 2.
- - If the versioning of a bucket is enabled or suspended, you can set NoncurrentVersionTransition or NoncurrentVersionExpiration to control the lifecycle of historical object versions. The lifecycle of a historical version depends on the time when it becomes a historical one (time when the version is replaced by a new version) and the value of NoncurrentDays. For object deletion, if NoncurrentDays is set to 1, an object version will be deleted only after it becomes a historical one for one day. If the version V1 of object A is created on the first date of a month and new version V2 is uploaded on the fifth date of the month, V1 becomes a historical version. At 00:00 on the seventh date of the month, V1 will expire. If an object version does not meet the deletion conditions, but NoncurrentDays is set to 1 and StorageClass is set to WARM, the version transitions to the Warm storage class one day after it has become a historical version. For example, the V1 version of object A is created on the first day of a month, and its new version V2 is uploaded on the fifth day of the month. Then V1 becomes a historical version. One day later, that is, at 0 o'clock of the seventh day, V1 transitions to the Warm storage class. The deletion or transition of the object after the expiration time may be delayed. The delay is within 48 hours.
- Objects are processed according to the following procedures, if their latest versions meet the expiration rule and versioning is enabled or suspended for the bucket.
- Versioning enabled:
If the latest version of the object does not have the DeleteMarker, the object generates a new DeleteMarker.
-If the object of the latest version has the DeleteMarker and the object has this version only, this version will be deleted.
+
|
Versioning status of the bucket.
Type: string
-Value options: Enabled, Suspended
+Value options: Enabled, Suspended
|
diff --git a/docs/obs/api-ref/obs_04_0039.html b/docs/obs/api-ref/obs_04_0039.html
index 92582cc9..915aac33 100644
--- a/docs/obs/api-ref/obs_04_0039.html
+++ b/docs/obs/api-ref/obs_04_0039.html
@@ -166,7 +166,7 @@ Authorization: authorization strin
Prefix or suffix of object names for filtering
Type: string
Ancestor: FilterRule
-Value options: prefix, suffix
+Value options: prefix, suffix
|
No
|
diff --git a/docs/obs/api-ref/obs_04_0040.html b/docs/obs/api-ref/obs_04_0040.html
index dbfdd841..1887f913 100644
--- a/docs/obs/api-ref/obs_04_0040.html
+++ b/docs/obs/api-ref/obs_04_0040.html
@@ -146,7 +146,7 @@ Content-Length: length
Prefix or suffix of object names for filtering
Type: string
Ancestor: FilterRule
-Value options: prefix, suffix
+Value options: prefix, suffix
|
|
DeleteData
diff --git a/docs/obs/api-ref/obs_04_0051.html b/docs/obs/api-ref/obs_04_0051.html
index 8a3c0c07..2967d42d 100644
--- a/docs/obs/api-ref/obs_04_0051.html
+++ b/docs/obs/api-ref/obs_04_0051.html
@@ -2,7 +2,7 @@
Deleting Tags
FunctionsThis operation deletes the tags of a bucket.
- To perform this operation, you must have the PutBucketTagging permission. By default, only the bucket owner can delete the tags of a bucket. The bucket owner can allow other users to perform this operation by setting a bucket policy or granting them the permission.
+ To perform this operation, you must have the DeleteBucketTagging permission. By default, only the bucket owner can delete the tags of a bucket. The bucket owner can allow other users to perform this operation by setting a bucket policy or granting them the permission.
Request Syntax1
2
diff --git a/docs/obs/api-ref/obs_04_0053.html b/docs/obs/api-ref/obs_04_0053.html
index 85634a10..e77131d7 100644
--- a/docs/obs/api-ref/obs_04_0053.html
+++ b/docs/obs/api-ref/obs_04_0053.html
@@ -1,7 +1,7 @@
Querying Bucket Storage Quota
-FunctionsOnly the bucket owner can query information about the bucket storage quota. However, an inactive owner is not allowed to get the bucket quota. The bucket storage quota is measured by byte. 0 indicates that no upper limit is set.
+ FunctionsA bucket owner can query the bucket storage quota, but a bucket owner who is frozen due to arrears cannot. The bucket storage quota is measured by byte. 0 indicates that no upper limit is set.
Request Syntax1
2
diff --git a/docs/obs/api-ref/obs_04_0062.html b/docs/obs/api-ref/obs_04_0062.html
index d77fa143..75af0837 100644
--- a/docs/obs/api-ref/obs_04_0062.html
+++ b/docs/obs/api-ref/obs_04_0062.html
@@ -90,7 +90,7 @@ Content-Length: length
|
Server-side encryption algorithm used for the default encryption configuration of a bucket.
Type: string
-Valid values: kms
+Value options: kms
Ancestor: ApplyServerSideEncryptionByDefault
|
Yes
@@ -101,7 +101,7 @@ Content-Length: length
| Customer master key (CMK) used in SSE-KMS encryption mode. If you do not specify this header, the default master key will be used.
Type: string
Valid value formats are as follows:
-- regionID:domainID (account ID):key/key_id
- key_id
+- regionID:domainID (account ID):key/key_id
- key_id
In the preceding formats:
- regionID indicates the ID of the region where the key resides.
- domainID indicates the ID of the domain to which the key belongs. For details, see Obtaining the Domain ID and User ID.
- key_id indicates the ID of the key created inKMS.
Ancestor: ApplyServerSideEncryptionByDefault
@@ -113,7 +113,7 @@ Content-Length: length
|
ID of the project to which the KMS master key belongs in the SSE-KMS mode.
Type: string
-Valid values:
+Value options:
- Project ID that matches KMSMasterKeyID.
- If KMSMasterKeyID is not specified, do not set the project ID.
Ancestor: ApplyServerSideEncryptionByDefault
|
diff --git a/docs/obs/api-ref/obs_04_0063.html b/docs/obs/api-ref/obs_04_0063.html
index b0af75ad..2c9b906e 100644
--- a/docs/obs/api-ref/obs_04_0063.html
+++ b/docs/obs/api-ref/obs_04_0063.html
@@ -100,7 +100,7 @@ Date: date
The server-side encryption algorithm used for encryption configuration of a bucket.
Type: string
-Valid value: kms
+Value options: kms
Ancestor: ApplyServerSideEncryptionByDefault
|
diff --git a/docs/obs/api-ref/obs_04_0068.html b/docs/obs/api-ref/obs_04_0068.html
new file mode 100644
index 00000000..bf7149a7
--- /dev/null
+++ b/docs/obs/api-ref/obs_04_0068.html
@@ -0,0 +1,128 @@
+
+
+Configuring the Requester-Pays Function for a Bucket
+FunctionsThe requester-pays configuration allows the requester to pay for data transfer and API calls associated with accessing the requested OBS resources, while the bucket owner only pays for data storage.
+ To access a requester-pays bucket, users (except the bucket owner and IAM users under the same account as the bucket owner) must add the x-obs-request-payer: requester header in the request, indicating that the requester agrees to pay for the request and traffic. If this header is not included in the request, the authentication fails and error "403 Forbidden" is returned. If the response returned by the server includes the x-obs-request-charged: requester header, the requester is billed for the request. This rule is applicable to all API requests against requester-pays buckets.
+
+
+
+ Request Syntax1
+2
+3
+4
+5
+6
+7
+8
+9 | PUT /?requestPayment HTTP/1.1
+Host: bucketname.obs.region.example.com
+Date: date
+Authorization: authorization
+Content-Length: length
+
+<RequestPaymentConfiguration>
+ <Payer>Payer</Payer>
+</RequestPaymentConfiguration>
+ |
+
+
+
+ Request ParametersThis request contains no message parameters.
+
+ Request HeadersThis request uses common headers. For details, see Table 3.
+
+ Request ElementsThis request contains elements that specify the requester-pays configuration for the bucket. Configuration information is uploaded in the XML format. The following table lists request elements.
+
+ Table 1 Elements for configuring the requester-pays functionElement
+ |
+Description
+ |
+Mandatory
+ |
+
|---|
+
+RequestPaymentConfiguration
+ |
+Root node of the requester-pays configuration.
+Ancestor: none
+ |
+Yes
+ |
+
+Payer
+ |
+Specifies who pays for accessing resources in the bucket.
+Type: string
+Ancestor: RequestPaymentConfiguration
+Value options:
+- BucketOwner: The bucket owner pays all fees associated with the bucket.
- Requester: The requester pays for data transfer and API calls associated with accessing resources in the bucket, while the bucket owner pays for data storage in the bucket.
+ |
+Yes
+ |
+
+
+
+
+
+ Response Syntax | HTTP/1.1 status_code
+Date: date
+Content-Length: length
+ |
+
+
+
+ Response HeadersThe response to the request uses common headers. For details, see Table 1.
+
+ Response ElementsThis response involves no elements.
+
+ Error ResponsesNo special error responses are returned. For details about error responses, see Table 2.
+
+ Sample Request 1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10 | PUT/?requestPayment HTTP/1.1
+User-Agent: curl/7.29.0
+Host: examplebucket.obs.region.example.com
+Accept: */*
+Date: Tue, 03 Mar 2020 12:07:05 GMT
+Authorization: OBS H4IPJX0TQTHTHEBQQCEC:5DGAS7SBbMC1YTC4tNXY57Zl2Fo=
+
+<RequestPaymentConfiguration>
+ <Payer>Requester</Payer>
+</RequestPaymentConfiguration>
+ |
+
+
+
+ Sample Response | HTTP/1.1 200 OK
+Server: OBS
+x-obs-request-id: 0000016A6C21AD79654C09D9AA45EB5D
+x-obs-id-2: 32AAAQAAEAABAAAQAAEAABAAAQAAEAABCSmfq4hegf1QZv8/ewfveE4B566v5DZ8
+Content-Type: application/xml
+Date: Tue, 30 Apr 2019 02:45:07 GMT
+Content-Length: 0
+ |
+
+
+
+ Obtaining the Requester-Pays Configuration Information of a Bucket
+FunctionsThis API obtains the requester-pays configuration information of a bucket.
+
+ Request Syntax | GET /?requestPayment HTTP/1.1
+Host: bucketname.obs.region.example.com
+Date: date
+Authorization: authorization
+Content-Length: length
+ |
+
+
+
+ Request ParametersThis request contains no message parameters.
+
+ Request HeadersThis request uses common headers. For details, see Table 3.
+
+ Request ElementsThis request involves no elements.
+
+ Response Syntax1
+2
+3
+4
+5
+6
+7
+8
+9 | HTTP/1.1 status_code
+Content-Type: type
+Date: date
+Content-Length: length
+
+<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
+<RequestPaymentConfiguration xmlns="http://obs.example.com/doc/2015-06-30/">
+ <Payer>Payer</Payer>
+</RequestPaymentConfiguration>
+ |
+
+
+
+ Response HeadersThe response to the request uses common headers. For details, see Table 1.
+
+ Response ElementsThis response contains the following elements:
+
+ Element
+ |
+Description
+ |
+
|---|
+
+RequestPaymentConfiguration
+ |
+Elements of the requester-pays configuration.
+Type: container
+ |
+
+Payer
+ |
+Identifier of who pays for the bucket.
+Type: string
+Ancestor: RequestPaymentConfiguration
+Value options:
+- BucketOwner: The bucket owner pays all fees associated with the bucket.
- Requester: The requester pays for data transfer and API calls associated with accessing resources in the bucket, while the bucket owner pays for data storage in the bucket.
+ |
+
+
+
+
+
+ Error ResponsesNo special error responses are returned. For details about error responses, see Table 2.
+
+ Sample Request | GET /?requestPayment HTTP/1.1
+User-Agent: curl/7.29.0
+Host: examplebucket.obs.region.example.com
+Accept: */*
+Date: Tue, 03 Mar 2020 12:07:05 GMT
+Authorization: OBS H4IPJX0TQTHTHEBQQCEC:5DGAS7SBbMC1YTC4tNXY57Zl2Fo=
+ |
+
+
+
+ Sample Response 1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12 | HTTP/1.1 200 OK
+Server: OBS
+x-obs-request-id: 0000016A6C21AD79654C09D9AA45EB5D
+x-obs-id-2: 32AAAQAAEAABAAAQAAEAABAAAQAAEAABCSmfq4hegf1QZv8/ewfveE4B566v5DZ8
+Content-Type: application/xml
+Date: Tue, 30 Apr 2019 02:45:07 GMT
+Content-Length: 0
+
+<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
+<RequestPaymentConfiguration xmlns="http://obs.example.com/doc/2015-06-30/">
+ <Payer>Requester</Payer>
+</RequestPaymentConfiguration>
+ |
+
+
+
+ Protocol used in the redirection request
Type: string
Ancestor: Redirect
-Value options: http, https
+Value options: http, https
Condition: Not required if one of the siblings is present.
|
No
diff --git a/docs/obs/api-ref/obs_04_0074.html b/docs/obs/api-ref/obs_04_0074.html
index 8615095b..737f23d7 100644
--- a/docs/obs/api-ref/obs_04_0074.html
+++ b/docs/obs/api-ref/obs_04_0074.html
@@ -110,7 +110,7 @@ Content-MD5: MD5
|
Method allowed by a CORS rule
Type: string
-Possible values are GET, PUT, HEAD, POST, and DELETE.
+Value options: GET, PUT, HEAD, POST, DELETE
Ancestor: CORSRule
|
Yes
diff --git a/docs/obs/api-ref/obs_04_0075.html b/docs/obs/api-ref/obs_04_0075.html
index 24d23ed4..75a0206d 100644
--- a/docs/obs/api-ref/obs_04_0075.html
+++ b/docs/obs/api-ref/obs_04_0075.html
@@ -81,7 +81,7 @@ Content-Length: length
|
Method allowed by a CORS rule.
Type: string
-Possible values are GET, PUT, HEAD, POST, and DELETE.
+Value options: GET, PUT, HEAD, POST, DELETE
Ancestor: CORSRule
|
diff --git a/docs/obs/api-ref/obs_04_0077.html b/docs/obs/api-ref/obs_04_0077.html
index 57ef01d6..43c4c123 100644
--- a/docs/obs/api-ref/obs_04_0077.html
+++ b/docs/obs/api-ref/obs_04_0077.html
@@ -48,7 +48,7 @@ Access-Control-Request-Method: method
An HTTP method that can be used by a request. The request can use multiple method headers.
Type: string
-Possible values are GET, PUT, HEAD, POST, and DELETE.
+Value options: GET, PUT, HEAD, POST, DELETE
|
Yes
|
@@ -118,7 +118,7 @@ Content-Length: length
If the Access-Control-Request-Method of a request meets server CORS configuration requirements, the response contains the methods in the rule.
Type: string
-Possible values are GET, PUT, HEAD, POST, and DELETE.
+Value options: GET, PUT, HEAD, POST, DELETE
|
Access-Control-Expose-Headers
diff --git a/docs/obs/api-ref/obs_04_0078.html b/docs/obs/api-ref/obs_04_0078.html
index 87913910..d4863153 100644
--- a/docs/obs/api-ref/obs_04_0078.html
+++ b/docs/obs/api-ref/obs_04_0078.html
@@ -46,7 +46,7 @@ Access-Control-Request-Method: method
|
Indicates an HTTP method that can be used by a request. The request can use multiple method headers.
Type: string
-Valid values: GET, PUT, HEAD, POST, and DELETE.
+Value options: GET, PUT, HEAD, POST, DELETE
|
Yes
|
@@ -116,7 +116,7 @@ Content-Length: length
If the Access-Control-Request-Method of a request meets server CORS configuration requirements, the response contains the methods in the rule.
Type: string
-Possible values are GET, PUT, HEAD, POST, and DELETE.
+Value options: GET, PUT, HEAD, POST, DELETE
|
Access-Control-Expose-Headers
diff --git a/docs/obs/api-ref/obs_04_0080.html b/docs/obs/api-ref/obs_04_0080.html
index 8cc3dbaf..87c597f0 100644
--- a/docs/obs/api-ref/obs_04_0080.html
+++ b/docs/obs/api-ref/obs_04_0080.html
@@ -1,7 +1,7 @@
Uploading Objects - PUT
-FunctionsAfter bucket creation in OBS, you can use this operation to upload an object to the bucket. Uploading an object adds it to a bucket. This requires users to have the write operation.
+ FunctionsAfter bucket creation in OBS, you can use this operation to upload an object to the bucket. This operation uploads an object to a bucket. To use this operation, you must have the write permission on the bucket.
The name of each object in a bucket must be unique.
With versioning not enabled, if an object to be uploaded has the same name as an existing object in the bucket, the newly uploaded object will overwrite the existing one. To protect data from being corrupted during transmission, you can add the Content-MD5 parameter in the request header. After receiving the request, OBS will perform an MD5 consistency check. If the two MD5 values are inconsistent, the system returns an error message.
@@ -72,7 +72,7 @@ Date: date
|
x-obs-grant-read
|
-When creating an object, you can use this header to authorize all users in an account the permission to read objects and obtain object metadata.
+ | When creating an object, you can use this header to grant all users in an account the permissions to read objects and obtain object metadata.
Type: string
Example: x-obs-grant-read: id=domainID. If multiple accounts are authorized, separate them with commas (,).
|
@@ -81,7 +81,7 @@ Date: date
x-obs-grant-read-acp
|
-When creating an object, you can use this header to authorize all users in an account the permission to obtain the object ACL.
+ | When creating an object, you can use this header to grant all users in an account the permissions to obtain the object ACL.
Type: string
Example: x-obs-grant-read-acp: id=domainID. If multiple accounts are authorized, separate them with commas (,).
|
@@ -90,7 +90,7 @@ Date: date
x-obs-grant-write-acp
|
-When creating an object, you can use this header to authorize all users in an account the permission to write the object ACL.
+ | When creating an object, you can use this header to grant all users in an account the permission to write the object ACL.
Type: string
Example: x-obs-grant-write-acp: id=domainID. If multiple accounts are authorized, separate them with commas (,).
|
@@ -99,7 +99,7 @@ Date: date
x-obs-grant-full-control
|
-When creating an object, you can use this header to authorize all users in an account the permission to read the object, obtain the object metadata, obtain the object ACL, and write the object ACL.
+ | When creating an object, you can use this header to grant all users in an account the permissions to read the object, obtain the object metadata, obtain the object ACL, and write the object ACL.
Type: string
Example: x-obs-grant-full-control: id=domainID. If multiple accounts are authorized, separate them with commas (,).
|
@@ -118,9 +118,10 @@ Date: date
x-obs-meta-*
|
-When creating an object, you can use a header starting with x-obs-meta- to define object metadata in an HTTP request. Custom metadata will be returned in the response header when you retrieve or query the metadata of the object.
+ | When creating an object, you can use a header starting with x-obs-meta- to define object metadata in an HTTP request. The user-defined metadata will be returned in the response when you retrieve the object or query the object metadata.
Type: string
Example: x-obs-meta-test: test metadata
+Constraint: Both user-defined metadata keys and their values must conform to US-ASCII standards.
|
No
|
@@ -150,7 +151,7 @@ Date: date
x-obs-server-side-encryption-kms-key-id
|
-Master key ID. This header is used in SSE-KMS mode. If the customer does not provide the master key ID, the default master key ID will be used.
+ | Master key ID. This header is used in SSE-KMS mode. If the customer does not provide the master key ID, the default master key ID will be used. If there is no such a default master key, the system will create one and use it by default.
Type: string
The following two formats are supported:
1. regionID:domainID:key/key_id
@@ -204,8 +205,8 @@ Date: date
|
x-obs-expires
|
-Indicates the expiration time of an object, in days. An object will be automatically deleted once it expires (calculated from the last modification time of the object).
-This field can be configured only when an object is uploaded and cannot be modified through the metadata modification API.
+ | Specifies when an object expires. It is measured in days. An object will be automatically deleted once it expires. (The validity calculates from the object's creation time.)
+You can configure this field when uploading an object or modify this field by using the metadata modification API after the object is uploaded.
Type: integer
Example: x-obs-expires:3
|
diff --git a/docs/obs/api-ref/obs_04_0081.html b/docs/obs/api-ref/obs_04_0081.html
index ec06ee17..8cceb329 100644
--- a/docs/obs/api-ref/obs_04_0081.html
+++ b/docs/obs/api-ref/obs_04_0081.html
@@ -175,7 +175,7 @@ Upload to OBS
file
|
-Indicates the content of the object to be uploaded.
+ | Specifies the object content uploaded. Both the file name and file path are ignored and will not be used as the object name. The object name is the value of parameter key.
Type: binary content or text
Constraint: This parameter must be the last parameter in a form. Otherwise, parameters after this parameter will be all discarded. Additionally, each request contains only one file parameter.
|
@@ -231,7 +231,7 @@ Upload to OBS
When creating an object, you can add this message header to set the permission control policy for the object. The predefined common policies are as follows: private, public-read, public-read-write, public-read-delivered, and public-read-write-delivered.
Type: string
-An example is provided as follows:
+Examples:
In POLICY: {"acl": "public-read" }
In HTML: <input type="text" name="acl" value="public-read" />
|
@@ -242,7 +242,7 @@ Upload to OBS
When creating an object, you can use this header to authorize all users in an account the permission to read objects and obtain object metadata.
Type: string
-An example is provided as follows:
+Examples:
In POLICY: {'grant-read': 'id=domainId1' },
In HTML: <input type="text" name="grant-read" value="id=domainId1" />
|
@@ -253,7 +253,7 @@ Upload to OBS
When creating an object, you can use this header to authorize all users in an account the permission to obtain the object ACL.
Type: string
-An example is provided as follows:
+Examples:
In POLICY: {"grant-read-acp": "id=domainId1" },
In HTML: <input type="text" name="grant-read-acp" value="id=domainId1" />
|
@@ -264,7 +264,7 @@ Upload to OBS
When creating an object, you can use this header to authorize all users in an account the permission to write the object ACL.
Type: string
-An example is provided as follows:
+Examples:
In POLICY: {"grant-write-acp": "id=domainId1" },
In HTML: <input type="text" name="grant-write-acp" value="id=domainId1" />
|
@@ -275,7 +275,7 @@ Upload to OBS
When creating an object, you can use this header to authorize all users in an account the permission to read the object, obtain the object metadata, obtain the object ACL, and write the object ACL.
Type: string
-An example is provided as follows:
+Examples:
In POLICY: {"grant-full-control": "id=domainId1" },
In HTML: <input type="text" name="grant-full-control" value="id=domainId1" />
|
@@ -287,7 +287,7 @@ Upload to OBS When creating an object, you can use this header to specify the storage class for the object. If you do not use this header, the object storage class is the default storage class of the bucket.
Type: string
Storage class value options: STANDARD (Standard), WARM (Warm), COLD (Cold). These values are case sensitive.
-An example is provided as follows:
+Examples:
In POLICY: {"storage-class": "STANDARD" },
In HTML: <input type="text" name="x-obs-storage-class" value="STANDARD" />
@@ -302,7 +302,7 @@ Upload to OBS
Standard HTTP headers. OBS records those headers. If you download the object or send the HEAD Object request, those parameter values are returned.
Type: string
-An example is provided as follows:
+Examples:
In POLICY: ["starts-with", "$Content-Type", "text/"],
In HTML: <input type="text" name="content-type" value="text/plain" />
|
@@ -314,7 +314,7 @@ Upload to OBS Indicates the address (URL) to which a successfully responded request is redirected.
- If the value is valid and the request is successful, OBS returns status code 303. Location contains success_action_redirect as well as the bucket name, object name, and object ETag.
- If this parameter value is invalid, OBS ignores this parameter. In such case, the Location header is the object address, and OBS returns the response code based on whether the operation succeeds or fails.
Type: string
-An example is provided as follows:
+Examples:
In POLICY: {"success_action_redirect": "http://123458.com"},
In HTML: <input type="text" name="success_action_redirect" value="http://123458.com" />
@@ -323,9 +323,9 @@ Upload to OBS
x-obs-meta-*
|
-Indicates user-defined metadata. When creating an object, you can use this header or a header starting with x-obs-meta- to define object metadata in an HTTP request. Custom metadata will be returned in the response header when you retrieve or query the metadata of the object.
+ | Indicates user-defined metadata. When creating an object, you can use this header or a header starting with x-obs-meta- to define object metadata in an HTTP request. The user-defined metadata will be returned in the response when you retrieve the object or query the object metadata.
Type: string
-An example is provided as follows:
+Examples:
In POLICY: {" x-obs-meta-test ": " test metadata " },
In HTML: <input type="text" name=" x-obs-meta-test " value=" test metadata " />
|
@@ -337,7 +337,7 @@ Upload to OBS Indicates the status code returned after the request is successfully received. Possible values are 200, 201, and 204.
- If this parameter is set to 200 or 204, the body in the OBS response message is empty.
- If this parameter is set to 201, the OBS response message contains an XML document that describes the response to the request.
- If the value is not set or if it is set to an invalid value, the OBS returns an empty document with a 204 status code.
Type: string
-An example is provided as follows:
+Examples:
In POLICY: ["starts-with", "$success_action_status", ""],
In HTML: <input type="text" name="success_action_status" value="200" />
@@ -364,13 +364,13 @@ Upload to OBS
x-obs-server-side-encryption-kms-key-id
|
-Master key ID. This header is used in SSE-KMS mode. If the customer does not provide the master key ID, the default master key ID will be used.
+ | Master key ID. This header is used in SSE-KMS mode. If the customer does not provide the master key ID, the default master key ID will be used. If there is no such a default master key, the system will create one and use it by default.
Type: string
The following two formats are supported:
1. regionID:domainID:key/key_id
2. key_id
regionID is the ID of the region to which the key belongs. domainID is the account ID of the tenant to which the key belongs. key_id is the key ID created in KMS.
-Example:
+Examples:
1. x-obs-server-side-encryption-kms-key-id: region:domainiddomainiddomainiddoma0001:key/4f1cd4de-ab64-4807-920a-47fc42e7f0d0
2. x-obs-server-side-encryption-kms-key-id:4f1cd4de-ab64-4807-920a-47fc42e7f0d0
|
@@ -470,7 +470,7 @@ ETag: etag
Indicates that methods in the rule are included in the response if Access-Control-Request-Method in the request meets the CORS configuration requirements when CORS is configured for buckets.
Type: string
-Possible values are GET, PUT, HEAD, POST, and DELETE.
+Value options: GET, PUT, HEAD, POST, DELETE
|
Access-Control-Expose-Headers
@@ -563,7 +563,23 @@ ETag: etag
43
44
45
-46 | POST / HTTP/1.1
+46
+47
+48
+49
+50
+51
+52
+53
+54
+55
+56
+57
+58
+59
+60
+61
+62 | POST / HTTP/1.1
Date: WED, 01 Jul 2015 04:15:23 GMT
Host: examplebucket.obs.region.example.com
Content-Type: multipart/form-data; boundary=7db143f50da2
@@ -600,6 +616,22 @@ Content-Disposition: form-data; na
Vk6rwO0Nq09BLhvNSIYwSJTRQ+k=
--7db143f50da2
+Content-Disposition: form-data; name="x-obs-persistent-headers"
+
+test:dmFsdWUx
+--7db143f50da2
+Content-Disposition: form-data; name="x-obs-grant-read"
+
+id=52f24s3593as5730ea4f722483579xxx
+--7db143f50da2
+Content-Disposition: form-data; name="x-obs-server-side-encryption"
+
+kms
+--7db143f50da2
+Content-Disposition: form-data; name="x-obs-website-redirect-location"
+
+http://www.example.com/
+--7db143f50da2
Content-Disposition: form-data; name="file"; filename="C:\Testtools\UpLoadFiles\object\1024Bytes.txt"
Content-Type: text/plain
@@ -844,7 +876,7 @@ Upload to OBS
Sample Response 3The response to the authentication using a token
+ Sample Response 3Response to authentication with a token
1
2
3
@@ -862,6 +894,173 @@ Date: Fri,09Sep 2022Sample Request 4Configure the object expiration time.
+POST / HTTP/1.1
+Date: WED, 01 Jul 2015 04:15:23 GMT
+Host: examplebucket.obs.region.example.com
+Content-Type: multipart/form-data; boundary=148828969260233905620870
+Content-Length: 1639
+Origin: www.example.com
+Access-Control-Request-Headers:acc_header_1
+
+--148828969260233905620870
+Content-Disposition: form-data; name="key"
+
+object01
+--148828969260233905620870
+Content-Disposition: form-data; name="AwsAccessKeyId"
+
+55445349414d5354554254455354303030303033
+--148828969260233905620870
+Content-Disposition: form-data; name="signature"
+
+396246666f6f42793872792f7a3958524f6c44334e4e69763950553d--7db143f50da2
+--148828969260233905620870
+Content-Disposition: form-data; name="policy"
+
+65794a6c65484270636d463061573975496a6f694d6a41794d7930774e6930784e565178...
+--148828969260233905620870
+Content-Disposition: form-data; name="x-obs-expires"
+
+4
+--148828969260233905620870
+Content-Disposition: form-data; name="file"; filename="test.txt"
+Content-Type: text/plain
+
+01234567890
+--148828969260233905620870
+Content-Disposition: form-data; name="submit"
+
+Upload
+--148828969260233905620870--
+ Sample Response 4Response to the configuration of object expiration time
+
+HTTP/1.1 204 No Content
+Server: OBS
+Date: Thu, 15 Jun 2023 12:39:03 GMT
+Connection: keep-alive
+Location: http://examplebucket.obs.region.example.com/my-obs-object-key-demo
+x-obs-expiration: expiry-date="Tue, 20 Jun 2023 00:00:00 GMT"
+ETag: "d41d8cd98f00b204e9800998ecf8427e"
+x-obs-request-id: 00000188BF11049553064911000FC30D
+x-obs-id-2: 32AAAUJAIAABAAAQAAEAABAAAQAAEAABCSwj2PcBE0YcoLHUDO7GSj+rVByzjflA
+x-forward-status: 0x40020000000001
+x-dae-api-type: REST.POST.OBJECT
+ Sample Request 5Set the status code of a successful action to 200.
+ POST /srcbucket HTTP/1.1
+User-Agent: PostmanRuntime/7.26.8
+Accept: */*
+Postman-Token: 667dcc44-1c48-41ba-9e41-9f87d8975089
+Host: obs.region.example.com
+Accept-Encoding: gzip, deflate, br
+Connection: keep-alive
+Content-Type: multipart/form-data; boundary=--------------------------285613759795901770404350
+Content-Length: 1134
+
+----------------------------285613759795901770404350
+Content-Disposition: form-data; name="key"
+
+obj
+----------------------------285613759795901770404350
+Content-Disposition: form-data; name="AwsAccessKeyId"
+
+XXXXXXXXXXXXXXX000003
+----------------------------285613759795901770404350
+Content-Disposition: form-data; name="signature"
+
+9rc4bVhDPQ7eHtw17hWtYxLnBWU=
+----------------------------285613759795901770404350
+Content-Disposition: form-data; name="policy"
+
+eyJleHBpcmF0aW9uIjoiMjAyMy0wNi0xNVQxNDoxMTozNFoiLCAiY29uZGl0aW9ucyI6W3siYnVja2V0Ijoic3JjYnVja2V0MiJ9LHsic3VjY2Vzc19hY3Rpb25fc3RhdHVzIjoiMjAwIn0seyJjb250ZW50LXR5cGUiOiJ0ZXh0L3BsYWluIn0seyJrZXkiOiIzMzMifSxdfQ==
+----------------------------285613759795901770404350
+Content-Disposition: form-data; name="success_action_status"
+
+200
+----------------------------285613759795901770404350
+Content-Disposition: form-data; name="file"; filename="test.txt"
+Content-Type: text/plain
+
+
+----------------------------285613759795901770404350
+Content-Disposition: form-data; name="submit"
+
+Upload to OBS
+----------------------------285613759795901770404350--
+ Sample Response 5Response to the configuration of success status code 200
+ HTTP/1.1 200 OK
+Server: OBS
+Date: Thu, 15 Jun 2023 13:12:51 GMT
+Content-Length: 0
+Connection: keep-alive
+Location: http://obs.region.example.com/srcbucket/obj
+ETag: "d41d8cd98f00b204e9800998ecf8427e"
+x-obs-request-id: 00000188BF2FF55F5306426E000FE366
+x-obs-id-2: 32AAAUJAIAABAAAQAAEAABAAAQAAEAABCScDjcXgZ7oMYSVnZnk4+HrClVwLVPTi
+x-forward-status: 0x40020000000001
+x-dae-api-type: REST.POST.OBJECT
+ Sample Request 6Configure a WORM retention policy when uploading an object.
+ POST /srcbucket HTTP/1.1
+User-Agent: PostmanRuntime/7.26.8
+Accept: */*
+Postman-Token: 4c2f4c7e-2e0b-46c0-b1a7-4a5da560b6a1
+Host: obs.region.example.com
+Accept-Encoding: gzip, deflate, br
+Connection: keep-alive
+Content-Type: multipart/form-data; boundary=--------------------------940435396775653808840608
+Content-Length: 1409
+
+----------------------------940435396775653808840608
+Content-Disposition: form-data; name="key"
+
+obj
+----------------------------940435396775653808840608
+Content-Disposition: form-data; name="AwsAccessKeyId"
+
+XXXXXXXXXXXXXXX000003
+----------------------------940435396775653808840608
+Content-Disposition: form-data; name="signature"
+
+X/7QiyMYUvxUWk0R5fToeTcgMMU=
+----------------------------940435396775653808840608
+Content-Disposition: form-data; name="policy"
+
+eyJleHBpcmF0aW9uIjoiMjAyMy0wNi0xNVQxNDoyMjo1MVoiLCAiY29uZGl0aW9ucyI6W3sieC1vYnMtb2JqZWN0LWxvY2stcmV0YWluLXVudGlsLWRhdGUiOiJUaHUsIDIwIEp1biAyMDIzIDEzOjEyOjUxIEdNVCJ9LHsieC1vYnMtb2JqZWN0LWxvY2stbW9kZSI6IkNPTVBMSUFOQ0UifSx7ImJ1Y2tldCI6InNyY2J1Y2tldDIifSx7ImNvbnRlbnQtdHlwZSI6InRleHQvcGxhaW4ifSx7ImtleSI6IjMzMyJ9LF19
+----------------------------940435396775653808840608
+Content-Disposition: form-data; name="x-obs-object-lock-mode"
+
+COMPLIANCE
+----------------------------940435396775653808840608
+Content-Disposition: form-data; name="x-obs-object-lock-retain-until-date"
+
+Thu, 20 Jun 2023 13:12:51 GMT
+----------------------------940435396775653808840608
+Content-Disposition: form-data; name="file"; filename="test.txt"
+Content-Type: text/plain
+
+
+----------------------------940435396775653808840608
+Content-Disposition: form-data; name="submit"
+
+Upload to OBS
+----------------------------940435396775653808840608--
+ Sample Response 6Response to an object-level WORM retention policy
+ HTTP/1.1 204 No Content
+Server: OBS
+Date: Thu, 15 Jun 2023 13:24:03 GMT
+Connection: keep-alive
+Location: http://obs.region.example.com/srcbucket/obj
+ETag: "d41d8cd98f00b204e9800998ecf8427e"
+x-obs-request-id: 00000188BF3A36EE5306427D000FEE0A
+x-obs-id-2: 32AAAUJAIAABAAAQAAEAABAAAQAAEAABCS/5pj0p0hAQcDVI3B6E5y167zy4eAQv
+x-forward-status: 0x40020000000001
+x-dae-api-type: REST.POST.OBJECT
+
diff --git a/docs/obs/api-ref/obs_04_0082.html b/docs/obs/api-ref/obs_04_0082.html
index e9b40715..e3260ef1 100644
--- a/docs/obs/api-ref/obs_04_0082.html
+++ b/docs/obs/api-ref/obs_04_0082.html
@@ -97,7 +97,7 @@ Date: date
|
Indicates names of the source bucket and the source object. If the source object has multiple versions, the versionId parameter can be used to specify the desired version.
Type: string
-Constraint: URL encoding is required for handling Chinese characters.
+Constraint: URL encoding is required for handling Chinese characters and %.
Example: x-obs-copy-source: /source_bucket/sourceObject
|
Yes
@@ -184,7 +184,7 @@ Date: date
|
x-obs-server-side-encryption-kms-key-id
|
-Indicates the master key ID of an encrypted object. This header is used in SSE-KMS mode. If the customer does not provide the master key ID, the default master key ID will be used.
+ | Indicates the master key ID of an encrypted object. This header is used in SSE-KMS mode. If the customer does not provide the master key ID, the default master key ID will be used. If there is no such a default master key, the system will create one and use it by default.
Type: string
The following two formats are supported:
1. regionID:domainID:key/key_id
diff --git a/docs/obs/api-ref/obs_04_0083.html b/docs/obs/api-ref/obs_04_0083.html
index 32cd20c3..2dcc9782 100644
--- a/docs/obs/api-ref/obs_04_0083.html
+++ b/docs/obs/api-ref/obs_04_0083.html
@@ -100,7 +100,7 @@ Range:bytes=byte_range
|
attname
|
-Rewrites the Content-Disposition header in the response.
+ | Rewrites the Content-Disposition header in the response.
Type: string
Example:
attname=name1
@@ -251,7 +251,7 @@ Last-Modified: time
|
Indicates whether an object is a deletion marker. If the object is not marked as deleted, the response does not contain this header.
Type: boolean
-Valid values: true or false
+Value options: true, false
The default value is false.
|
diff --git a/docs/obs/api-ref/obs_04_0084.html b/docs/obs/api-ref/obs_04_0084.html
index 61290d61..681a4649 100644
--- a/docs/obs/api-ref/obs_04_0084.html
+++ b/docs/obs/api-ref/obs_04_0084.html
@@ -167,7 +167,7 @@ Last-Modified: time
Indicates that methods in the rule are included in the response if Access-Control-Request-Method in the request meets the CORS configuration requirements when CORS is configured for buckets.
Type: string
-Possible values are GET, PUT, HEAD, POST, and DELETE.
+Value options: GET, PUT, HEAD, POST, DELETE
|
Access-Control-Expose-Headers
diff --git a/docs/obs/api-ref/obs_04_0085.html b/docs/obs/api-ref/obs_04_0085.html
index 27c14cda..c46b837a 100644
--- a/docs/obs/api-ref/obs_04_0085.html
+++ b/docs/obs/api-ref/obs_04_0085.html
@@ -65,7 +65,7 @@ Date: date
|
Indicates whether an object is deleted. If the object is not marked as deleted, the response does not contain this header.
Type: boolean
-Valid values: true or false
+Value options: true, false
The default value is false.
|
diff --git a/docs/obs/api-ref/obs_04_0089.html b/docs/obs/api-ref/obs_04_0089.html
index dcaf93d9..330825be 100644
--- a/docs/obs/api-ref/obs_04_0089.html
+++ b/docs/obs/api-ref/obs_04_0089.html
@@ -135,7 +135,7 @@ Authorization: authorization
Permission
|
Authorized permission.
-Value options: READ | READ_ACP | WRITE_ACP | FULL_CONTROL
+Value options: READ, READ_ACP, WRITE_ACP, FULL_CONTROL
Type: string
|
No
diff --git a/docs/obs/api-ref/obs_04_0098.html b/docs/obs/api-ref/obs_04_0098.html
index ad147dc6..8f405709 100644
--- a/docs/obs/api-ref/obs_04_0098.html
+++ b/docs/obs/api-ref/obs_04_0098.html
@@ -49,7 +49,7 @@ Authorization: authorization
| x-obs-acl
|
-When initializing a multipart upload task, you can add this message header to set the permission control policy for the object. The predefined common policies are as follows: private, public-read, and public-read-write.
+ | When initiating a multipart upload, you can add this message header to set the permission control policy for the object. The predefined common policies are as follows: private, public-read, and public-read-write.
Type: string
Note: This header is a predefined policy expressed in a character string.
Example: x-obs-acl: public-read-write
@@ -59,7 +59,7 @@ Authorization: authorization
|
x-obs-grant-read
|
-When initializing a multipart upload task, you can use this header to authorize all users in an account to read the object and obtain the object metadata.
+ | When initiating a multipart upload, you can use this header to authorize all users in an account to read the object and obtain the object metadata.
Type: string
Example: x-obs-grant-read: ID=domainID If multiple accounts are authorized, separate them with commas (,).
|
@@ -68,7 +68,7 @@ Authorization: authorization
x-obs-grant-read-acp
|
-When initializing a multipart upload task, you can use this header to authorize all users in an account the permission to obtain the object ACL.
+ | When initiating a multipart upload, you can use this header to authorize all users in an account the permission to obtain the object ACL.
Type: string
Example: x-obs-grant-read-acp: ID=domainID If multiple accounts are authorized, separate them with commas (,).
|
@@ -77,7 +77,7 @@ Authorization: authorization
x-obs-grant-write-acp
|
-When initializing a multipart upload task, you can use this header to authorize all users in an account the permission to write the object ACL.
+ | When initiating a multipart upload, you can use this header to authorize all users in an account the permission to write the object ACL.
Type: string
Example: x-obs-grant-write-acp: ID=domainID If multiple accounts are authorized, separate them with commas (,).
|
@@ -86,7 +86,7 @@ Authorization: authorization
x-obs-grant-full-control
|
-When initializing a multipart upload task, you can use this header to authorize all users in an account the permission to read the object, obtain the object metadata, obtain the object ACL, and write the object ACL.
+ | When initiating a multipart upload, you can use this header to authorize all users in an account to read the object, obtain the object metadata, obtain the object ACL, and write the object ACL.
Type: string
Example: x-obs-grant-full-control: ID=domainID If multiple accounts are authorized, separate them with commas (,).
|
@@ -95,7 +95,7 @@ Authorization: authorization
x-obs-storage-class
|
-When initiating a multi-part upload task, you can add this header to specify the storage class for the object. If you do not use this header, the object storage class is the default storage class of the bucket.
+ | When initiating a multipart upload, you can add this header to specify the storage class for the object. If you do not use this header, the object storage class is the default storage class of the bucket.
Type: string
Storage class value options: STANDARD (Standard), WARM (Warm), COLD (Cold). These values are case sensitive.
Example: x-obs-storage-class: STANDARD
@@ -124,7 +124,7 @@ Authorization: authorization
|
x-obs-server-side-encryption-kms-key-id
|
-Master key ID. This header is used in SSE-KMS mode. If the customer does not provide the master key ID, the default master key ID will be used.
+ | Master key ID. This header is used in SSE-KMS mode. If the customer does not provide the master key ID, the default master key ID will be used. If there is no such a default master key, the system will create one and use it by default.
Type: string
The following two formats are supported:
1. regionID:domainID:key/key_id
@@ -176,6 +176,15 @@ Authorization: authorization
| No
|
+x-obs-meta-*
+ |
+When initiating a multipart upload, you can use a header starting with x-obs-meta- in the HTTP request to define object metadata for easy management. The user-defined metadata will be returned in the response when you retrieve the object or query the object metadata.
+Type: string
+Example: x-obs-meta-test: test metadata
+ |
+No
+ |
+
diff --git a/docs/obs/api-ref/obs_04_0101.html b/docs/obs/api-ref/obs_04_0101.html
index cd00cd9e..aaf508a3 100644
--- a/docs/obs/api-ref/obs_04_0101.html
+++ b/docs/obs/api-ref/obs_04_0101.html
@@ -20,7 +20,7 @@ Authorization: auth
uploadId
|
-Indicates a multipart upload ID.
+ | ID of the multipart upload
Type: string
Default value: none
|
@@ -29,8 +29,8 @@ Authorization: auth
max-parts
|
-Specifies the maximum number of parts to be listed.
-Type: string
+ | Maximum number of parts that can be listed
+Type: integer
Default value: 1000
|
No
@@ -39,8 +39,8 @@ Authorization: auth
| part-number
-marker
|
-Indicates the part after which the part listing begins. OBS lists only parts with greater numbers than that specified by this parameter.
-Type: string
+ | Part after which the part listing begins. OBS lists only parts with greater numbers than that specified by this parameter.
+Type: integer
Default value: none
|
No
@@ -123,7 +123,7 @@ Content-Length: length
| ListPartsResult
|
-Indicates the container for responses to List Parts requests.
+ | Container for responses to part listing requests
Type: container
Children: Bucket, Key, UploadId, PartNumberMarker, NextPartNumberMarker, MaxParts, IsTruncated, Part
Ancestor: none
@@ -131,28 +131,28 @@ Content-Length: length
|
Bucket
|
-Indicates a bucket name.
+ | Name of the bucket
Type: string
Ancestor: ListPartsResult
|
Key
|
-Indicates an object name.
+ | Object name
Type: string
Ancestor: ListPartsResult
|
UploadId
|
-Indicates the ID of a multipart upload.
+ | ID of the multipart upload
Type: string
Ancestor: ListPartsResult
|
Initiator
|
-Indicates the initiator of a multipart upload.
+ | Initiator of the multipart upload
Type: container
Children: ID
Ancestor: ListPartsResult
@@ -168,29 +168,29 @@ Content-Length: length
|
ID
|
-ID of the domain to which the owner belongs
+ | ID of the domain where the owner belongs
Type: string
Ancestor: Initiator or Owner
|
StorageClass
|
-Indicates the storage type.
+ | Storage class
Type: string
-Value options: STANDARD | WARM | COLD
+Value options: STANDARD, WARM, COLD
Ancestor: ListPartsResult
|
PartNumberMarker
|
-Part number after which listing parts begins.
+ | Part number after which listing parts begins
Type: integer
Ancestor: ListPartsResult
|
NextPartNumberMarker
|
-Indicates the value of PartNumberMarker in the next request when the returned result is incomplete.
+ | Value of PartNumberMarker in the next request when the returned result is incomplete
Type: integer
Ancestor: ListPartsResult
|
@@ -204,14 +204,14 @@ Content-Length: length
IsTruncated
|
-Indicates whether the returned part list is truncated. true: Not all results are returned. false: All results have been returned.
+ | Whether the returned part list is truncated. true: Not all results are returned. false: All results have been returned.
Type: boolean
Ancestor: ListPartsResult
|
Part
|
-Indicates the container for elements related to a particular part.
+ | Container for elements related to a particular part.
Type: string
Children: PartNumber, LastModified, ETag, Size
Ancestor: ListPartsResult
@@ -227,7 +227,7 @@ Content-Length: length
|
LastModified
|
-Indicates the date and time a part was uploaded.
+ | When a part was uploaded
Type: date
Ancestor: ListPartsResult.Part
|
@@ -241,7 +241,7 @@ Content-Length: length
Size
|
-Indicates the size of an uploaded part.
+ | Size of an uploaded part
Type: integer
Ancestor: ListPartsResult.Part
|
diff --git a/docs/obs/api-ref/obs_04_0113.html b/docs/obs/api-ref/obs_04_0113.html
index 4903b2be..a93e7aed 100644
--- a/docs/obs/api-ref/obs_04_0113.html
+++ b/docs/obs/api-ref/obs_04_0113.html
@@ -6,8 +6,6 @@
+403 Forbidden
+ |
+RequestPayerDenied
+ |
+This is a requester-pays bucket.
+ |
+Carry the header x-obs-request-payer: requester in the access request.
+ |
+
404 Not Found
|
NoSuchBucket
@@ -726,6 +735,15 @@ QUFBQUFBYmJiYmJiYmJD</HostId> The method is not allowed.
|
+405 Method Not Allowed
+ |
+FsNotSupport
+ |
+POSIX buckets do not support this API.
+ |
+The method is not allowed.
+ |
+
408 Request Timeout
|
RequestTimeout
@@ -865,9 +883,4 @@ QUFBQUFBYmJiYmJiYmJD</HostId>
-
diff --git a/docs/obs/api-ref/obs_04_0116.html b/docs/obs/api-ref/obs_04_0116.html
index 242aedb4..949cd949 100644
--- a/docs/obs/api-ref/obs_04_0116.html
+++ b/docs/obs/api-ref/obs_04_0116.html
@@ -2,7 +2,7 @@
Obtaining Access Keys (AK/SK)
When you call APIs, you need to use the AK and SK for authentication. To obtain the AK and SK, perform the following steps:
- - Log in to the console.
- Hover the cursor over the username in the upper right corner and choose My Credentials from the drop-down list.
- On the My Credentials page, click Manage Access Keys.
- Click Add Access Key.
- Enter the password for login.
- Enter the authentication code your email received.
- Click OK to download the access key file.
Keep AKs and SKs properly to prevent information leakage.
+ - Log in to the console.
- Click the login username in the upper right corner and choose My Credentials from the drop-down list.
- Choose Access Keys.
- Click Create Access Key.
- Enter the login password.
- Enter the verification code your mobile phone, or email received, and click OK.
- View the access key file that was automatically downloaded.
Keep AKs and SKs properly to prevent information leakage.
diff --git a/docs/obs/api-ref/obs_04_0160.html b/docs/obs/api-ref/obs_04_0160.html
index 8e4efd71..09a1949b 100644
--- a/docs/obs/api-ref/obs_04_0160.html
+++ b/docs/obs/api-ref/obs_04_0160.html
@@ -61,6 +61,7 @@ Authorization: authorization
|
Separator used to group object names. If a prefix is specified, objects with the same string from the prefix to the first delimiter are grouped into one CommonPrefixes. If no prefix is specified, objects with the same string from the first character to the first delimiter are grouped into one CommonPrefixes.
For example, there are three objects (abcd, abcde, and bbcde) in a bucket. If delimiter is set to d and prefix is set to a, objects abcd and abcde are grouped into a CommonPrefixes with abcd as the prefix. If only delimiter is set to d, objects abcd and abcde are grouped into a CommonPrefixes with abcd as the prefix, and bbcde is grouped separately into another CommonPrefixes with bbcd as the prefix.
+For a parallel file system, if this parameter is not specified, all the content in the directory is recursively listed by default, and subdirectories are also listed. In big data scenarios, parallel file systems usually have deep directory levels and each directory has a large number of files. In such case, you are advised to configure [delimiter=/] to list the content in the current directory, but not list subdirectories, thereby improving the listing efficiency.
Type: string
|
No
@@ -172,7 +173,7 @@ Content-Length: length
|
ETag
|
-Base64-encoded 128-bit MD5 digest of an object. ETag is the unique identifier of the object content. It can be used to determine whether the object content is changed. For example, if the ETag value is A when an object is uploaded, but this value has changed to B when the object is downloaded, it indicates that the object content has been changed. The ETag value is a hash of the object. The ETag reflects changes only to the object content, rather than its metadata. An uploaded object or copied object has a unique ETag after being encrypted using MD5. (If the object is encrypted on the server side, the ETag value is not the MD5 digest of the object, but the unique identifier calculated through server-side encryption.)
+ | Base64-encoded 128-bit MD5 digest of an object. ETag is the unique identifier of the object content. It can be used to determine whether the object content is changed. For example, if the ETag value is A when an object is uploaded, but this value has changed to B when the object is downloaded, it indicates that the object content has been changed. The ETag value is a hash of the object. The ETag reflects changes to the object content, rather than the object metadata. An uploaded object or copied object has a unique ETag after being encrypted using MD5. (If the object is encrypted on the server side, the ETag value is not the MD5 digest of the object, but the unique identifier calculated through server-side encryption.)
Type: string
Ancestor: ListBucketResult.Contents
|
@@ -251,7 +252,7 @@ Content-Length: length
Storage class of an object
Type: string
-Value options: STANDARD | WARM | COLD
+Value options: STANDARD, WARM, COLD
Ancestor: ListBucketResult.Contents
|
|
|
|