You can create buckets with different storage classes. The x-obs-storage-class header in a bucket creation request specifies the storage class for a bucket. If you do not specify a storage class when you upload an object to the bucket, the object inherits the storage class of the bucket. There are three storage classes: STANDARD (Standard storage class), WARM (Warm storage class), and COLD (Cold storage class) If this header is not in the request, the storage class of the created bucket is Standard.
x-obs-storage-class
|
-When creating a bucket, you can add this header to set the default storage class of the bucket. The default storage classes are as follows: STANDARD (Standard storage class), WARM (Warm storage class), and COLD (Cold storage class). If this header is not in the request, the storage class of the bucket created is Standard.
+ | When creating a bucket, you can add this header to specify the default storage class of the bucket. The default storage classes are as follows: STANDARD (Standard storage class), WARM (Warm storage class), and COLD (Cold storage class). If this header is not in the request, the storage class of the bucket created is Standard.
Type: string
|
No
diff --git a/docs/obs/api-ref/obs_04_0026.html b/docs/obs/api-ref/obs_04_0026.html
index 183a3d54d..e286c5560 100644
--- a/docs/obs/api-ref/obs_04_0026.html
+++ b/docs/obs/api-ref/obs_04_0026.html
@@ -36,6 +36,12 @@
Obtaining Bucket Storage Class Information
+Configuring Cross-Region Replication for a Bucket
+
+Obtaining the Cross-Region Replication Configuration of a Bucket
+
+Deleting the Cross-Region Replication Configuration of a Bucket
+
Configuring Tags for a Bucket
Obtaining Bucket Tags
diff --git a/docs/obs/api-ref/obs_04_0034.html b/docs/obs/api-ref/obs_04_0034.html
index 102dd7d1d..4d0425b63 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.
-  Objects are permanently deleted upon the expiration of their lifecycle time, and the deleted objects cannot be restored.
+ - 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:
@@ -126,7 +126,8 @@ Content-MD5: MD5
If the object of the latest version has the DeleteMarker and the object has this version only, this version will be deleted.
If the object of the latest version has the DeleteMarker and the object has other versions, all versions of the object remain unchanged.
- The following lists the processing when the versioning is enabled or suspended for a bucket and objects of the latest versions meet the transition rules:If the latest version of the object has the DeleteMarker, the storage class of this version will not be transitioned.If the latest version of the object does not have the DeleteMarker and meets the transition rule, the storage class of this version will be transitioned.
+ The following lists the processing when the versioning is enabled or suspended for a bucket and objects of the latest versions meet the transition rules:- If the latest version of the object has the DeleteMarker, the storage class of this version will not be transitioned.
- If the latest version of the object does not have the DeleteMarker and meets the transition rule, the storage class of this version will be transitioned.
+
Table 2 Response elements for lifecycle configurationName
|
@@ -219,7 +220,7 @@ Content-MD5: MD5
Children node: NoncurrentDays, StorageClass
Ancestor node: Rule
-Required if the Transition, Expiration, AbortIncompleteMultipartUpload, or NoncurrentVersionExpiration element is absent.
+ | Required if the Transition, Expiration, AbortIncompleteMultipartUpload, or NoncurrentVersionExpiration element is absent.
|
|---|
NoncurrentVersionExpiration
@@ -255,7 +256,7 @@ Content-MD5: MD5
|
Prefix
|
-Object name prefix identifying one or more objects to which the rule applies.
+ | Object name prefix that identifies one or more objects to which the rule applies.
Type: string
Ancestor node: Rule
Constraints:
@@ -298,7 +299,7 @@ Content-Length: length
Response HeadersThe response to the request uses common headers. For details, see Table 1.
Response ElementsThis response contains no elements.
+ Response ElementsThis response involves no elements.
Error ResponsesNo special error responses are returned. For details about error responses, see Table 2.
diff --git a/docs/obs/api-ref/obs_04_0044.html b/docs/obs/api-ref/obs_04_0044.html
index 5ea1016f0..dfbb90951 100644
--- a/docs/obs/api-ref/obs_04_0044.html
+++ b/docs/obs/api-ref/obs_04_0044.html
@@ -46,7 +46,7 @@ Authorization: authorization
Specifies the default storage class for a bucket.
Type: string
Value options: STANDARD | WARM | COLD
-There are three storage classes: STANDARD (Standard storage class), WARM (Warm storage class), and COLD (Cold storage class) Therefore, the following values can be configured: STANDARD, WARM, and COLD.
+The available storage classes include Standard (STANDARD), Warm (WARM), and Cold (COLD).
|
Yes
|
diff --git a/docs/obs/api-ref/obs_04_0046.html b/docs/obs/api-ref/obs_04_0046.html
new file mode 100644
index 000000000..fdb55a658
--- /dev/null
+++ b/docs/obs/api-ref/obs_04_0046.html
@@ -0,0 +1,286 @@
+
+
+ Configuring Cross-Region Replication for a Bucket
+ FunctionsCross-region replication refers to the automatic and asynchronous replication of objects across buckets in different regions. By activating the cross-region replication function, OBS can copy new objects and modified objects from a source bucket to destination buckets in different regions.
+ The following two requirements must be met when configuring the cross-region replication for a bucket:
+ - Cross-region replication can be configured only when the versioning statuses of the source and destination buckets are the same. For details about how to configure bucket versioning, see Configuring Versioning for a Bucket.
- The owner and agency (OBS) of the source bucket must have the permission to write the destination bucket (configured with BucketPolicy), and the agency (OBS) must have the read permission for the source bucket. This permission delegation needs to be implemented by calling the BucketPolicy API.
+ For details about how to configure the bucket policy, see Configuring a Bucket Policy. After the bucket policy is set, the agency (OBS) can read objects from the source bucket and copy objects to the destination bucket.
+
+ Request Syntax 1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21 | PUT /?replication HTTP/1.1
+Host: bucketname.obs.region.example.com
+x-obs-date: date
+Content-MD5: MD5
+Authorization: authorization string
+Content-Length: contentlength
+
+<ReplicationConfiguration>
+ <Agency>testAcy</Agency>
+ <Rule>
+ <ID>rule1</ID>
+ <Prefix>key-prefix</Prefix>
+ <Status>rule-status</Status>
+ <Destination>
+ <Bucket>targetbucketname</Bucket>
+ <StorageClass>STANDARD</StorageClass>
+ <DeleteData>Enabled</DeleteData>
+ </Destination>
+ <HistoricalObjectReplication>Enabled</HistoricalObjectReplication>
+ </Rule>
+</ReplicationConfiguration>
+ |
+
+
+
+ Request ParametersThis request contains no message parameters.
+
+ Request HeadersThe request uses one header, as described in the following table.
+
+ Table 1 Request header for cross-region replicationElement
+ |
+Description
+ |
+Mandatory
+ |
+
|---|
+
+Content-MD5
+ |
+Base64-encoded 128-bit MD5 digest of the message according to RFC 1864.
+ |
+Yes
+ |
+
+
+
+
+
+ Request ElementsThis request contains elements to specify the replication configuration for the bucket in XML format. The following table lists request elements:
+
+ Table 2 Bucket replication configuration elementsElement
+ |
+Description
+ |
+Mandatory
+ |
+
|---|
+
+ReplicationConfiguration
+ |
+Container for the replication rules. A maximum of 100 rules can be configured. The size of the XML file can reach 50 KB.
+Type: container
+Children: Rule
+Ancestor: none
+ |
+Yes
+ |
+
+Agency
+ |
+Name of the agency, which can have a maximum of 64 characters.
+Type: string
+Ancestor: ReplicationConfiguration
+ |
+Yes
+ |
+
+Rule
+ |
+Container of a specified replication rule.
+The replication configuration must contain at least one rule. The maximum number of rules is 100.
+Type: container
+Ancestor:
+ReplicationConfiguration
+ |
+Yes
+ |
+
+ID
+ |
+Unique identifier of a rule, with a maximum length of 255 characters.
+Type: string
+Ancestor: Rule
+ |
+No
+ |
+
+Status
+ |
+If the value of this element is Disabled, this rule will be ignored.
+Type: string
+Ancestor: Rule
+Value options: Enabled, Disabled
+ |
+Yes
+ |
+
+Prefix
+ |
+Prefix of an object key name, applicable to one or more objects. If the Prefix is left blank, the cross-region replication rule is applied to the whole bucket.
+The maximum length of a prefix is 1024 characters. Duplicated prefixes are not supported.
+Type: string
+Ancestor: Rule
+ |
+Yes
+ |
+
+Destination
+ |
+Container for the destination bucket information.
+Type: container
+Ancestor: Rule
+ |
+Yes
+ |
+
+Bucket
+ |
+Bucket used to store object copies that are marked by rules.
+If the replication configuration contains multiple rules, the rules must specify the same bucket as the destination bucket.
+Type: string
+Ancestor: Destination
+ |
+Yes
+ |
+
+StorageClass
+ |
+Storage class of an object
+Type: string
+Ancestor: Destination
+Value options: STANDARD | WARM | COLD
+ |
+No
+ |
+
+DeleteData
+ |
+Keyword for synchronizing object deletion operations. If the value is Enabled, the object deletion for the source bucket will be replicated to the destination bucket.
+Type: string
+Ancestor: Destination
+Value options: Enabled and Disabled (If this element is absent from the request, Disabled is applied by default.)
+ |
+No
+ |
+
+HistoricalObjectReplication
+ |
+Keyword for copying a historical object. If the value is Enabled, historical objects meeting this rule are copied.
+Type: string
+Ancestor: Rule
+Value options: Enabled and Disabled (If this element is absent from the request, Disabled is applied by default.)
+ |
+No
+ |
+
+
+
+
+
+ Response Syntax | HTTP/1.1 status_code
+Server: OBS
+Date:date
+Content-Length: contentlength
+ |
+
+
+
+ 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 this request.
+
+ Sample Request 1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23 | PUT /?replication HTTP/1.1
+User-Agent: curl/7.29.0
+Host: examplebucket.obs.region.example.com
+Accept: */*
+Date: Wed, 27 Jun 2018 13:39:15 +0000
+Authorization: OBS H4IPJX0TQTHTHEBQQCEC:CdeqU0Vg9xNdJMZ0PGPgh5EnkO0=
+Content-MD5: l/Z8mfSX+VyV8k5EhIQz5Q==
+Content-Length: 330
+
+<ReplicationConfiguration>
+ <Agency>testAcy</Agency>
+ <Rule>
+ <ID>Rule-1</ID>
+ <Status>Enabled</Status>
+ <Prefix></Prefix>
+ <Destination>
+ <Bucket>dstbucket</Bucket>
+ <StorageClass>STANDARD</StorageClass>
+ <DeleteData>Enabled</DeleteData>
+ </Destination>
+ <HistoricalObjectReplication>Enabled</HistoricalObjectReplication>
+ </Rule>
+</ReplicationConfiguration>
+ |
+
+
+
+ Sample Response | HTTP/1.1 200 OK
+Server: OBS
+x-obs-request-id: B59500000164417839932E5A2295674C
+x-obs-id-2: 32AAAQAAEAABKAAQAAEAABAAAQAAEAABCStv51t2NMMx+Ou+ow7IWV4Sxo231fKe
+Date: Wed, 27 Jun 2018 13:39:15 GMT
+Content-Length: 0
+ |
+
+
+
+
+
+
diff --git a/docs/obs/api-ref/obs_04_0047.html b/docs/obs/api-ref/obs_04_0047.html
new file mode 100644
index 000000000..05a6d0764
--- /dev/null
+++ b/docs/obs/api-ref/obs_04_0047.html
@@ -0,0 +1,260 @@
+
+
+ Obtaining the Cross-Region Replication Configuration of a Bucket
+ FunctionsThis operation obtains the replication configuration information of a specified bucket. To perform this operation, you must have the GetReplicationConfiguration permission.
+
+ Request Syntax | GET /?replication HTTP/1.1
+Host: bucketname.obs.region.example.com
+Date: date
+Authorization:authorization string
+ |
+
+
+
+ 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 Syntax 1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20 | HTTP/1.1 status_code
+Date: date
+Server:OBS
+Content-Length: contentlength
+
+<?xml version="1.0" encoding="UTF-8"?>
+<ReplicationConfiguration xmlns="http://obs.example.com/doc/2006-03-01/">
+ <Agency>testAcy</Agency>
+ <Rule>
+ <ID>rule1</ID>
+ <Status>Enabled</Status>
+ <Prefix></Prefix>
+ <Destination>
+ <Bucket>exampletargetbucket</Bucket>
+ <StorageClass>WARM</StorageClass>
+ <DeleteData>Enabled</DeleteData>
+ </Destination>
+ <HistoricalObjectReplication>Enabled</HistoricalObjectReplication>
+ </Rule>
+</ReplicationConfiguration>
+ |
+
+
+
+ Response HeadersThe response to the request uses common headers. For details, see Table 1.
+
+ Response ElementsThis response contains elements to detail the configuration. The following table describes the elements.
+
+ Table 1 Bucket replication configuration elementsElement
+ |
+Description
+ |
+
|---|
+
+ReplicationConfiguration
+ |
+Container for the replication rules. A maximum of 100 rules can be configured. The size of the XML file can reach 50 KB.
+Type: container
+Children: Rule
+Ancestor: none
+ |
+
+Agency
+ |
+Name of the agency, which can have a maximum of 64 characters.
+Type: string
+Ancestor: ReplicationConfiguration
+ |
+
+Rule
+ |
+Container of a specified replication rule.
+The replication configuration must contain at least one rule. The maximum number of rules is 100.
+Type: container
+Ancestor: ReplicationConfiguration
+ |
+
+ID
+ |
+Unique identifier of a rule, with a maximum length of 255 characters.
+Type: string
+Ancestor: Rule
+ |
+
+Status
+ |
+If the value of this element is Disabled, this rule will be ignored.
+Type: string
+Ancestor: Rule
+Value options: Enabled and Disabled
+ |
+
+Prefix
+ |
+Prefix of an object key name, applicable to one or more objects. If the Prefix is left blank, the cross-region replication rule is applied to the whole bucket.
+The maximum length of a prefix is 1,024 characters. Duplicated prefixes are not supported.
+Type: string
+Ancestor: Rule
+ |
+
+Destination
+ |
+Container for the destination bucket information.
+Type: container
+Ancestor: Rule
+ |
+
+Bucket
+ |
+Bucket used to store object copies that are marked by rules.
+If the replication configuration contains multiple rules, the rules must specify the same bucket as the destination bucket.
+Type: string
+Ancestor: Destination
+ |
+
+StorageClass
+ |
+Storage class of an object.
+Type: string
+Ancestor: Destination
+Value options: STANDARD | WARM | COLD
+ |
+
+DeleteData
+ |
+Keyword for synchronizing object deletion operations. If the value is Enabled, the object deletion for the source bucket will be replicated to the destination bucket.
+Type: string
+Ancestor: Destination
+Value options: Enabled and Disabled (If this element is absent from the request, Disabled is applied by default.)
+ |
+
+HistoricalObjectReplication
+ |
+Keyword for copying a historical object. If the value is Enabled, historical objects meeting this rule are copied.
+Type: string
+Ancestor: Rule
+Value options: Enabled and Disabled (If this element is absent from the request, Disabled is applied by default.)
+ |
+
+
+
+
+
+ Error ResponsesThe following table describes the error response for this request.
+
+ Table 2 Error response elementsError Code
+ |
+Description
+ |
+HTTP Response Code
+ |
+SOAP Error Code Prefix
+ |
+
|---|
+
+NoSuchReplicationConfiguration
+ |
+Cross-region replication configuration does not exist.
+ |
+404 not found
+ |
+Client
+ |
+
+
+
+
+
+ Sample Request | GET /?replication HTTP/1.1
+User-Agent: curl/7.29.0
+Host: examplebucket.obs.region.example.com
+Accept: */*
+Date: Wed, 27 Jun 2018 13:42:40 +0000
+Authorization: OBS H4IPJX0TQTHTHEBQQCEC:jGHviInfRyOkT/EpySpua1hlBuY=
+ |
+
+
+
+ Sample Response 1
+ 2
+ 3
+ 4
+ 5
+ 6
+ 7
+ 8
+ 9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23 | HTTP/1.1 200 OK
+Server: OBS
+x-obs-request-id: B59500000164417B57D02F7EF8823152
+x-obs-id-2: 32AAAQAAEAABAAAQAAEAABAAAQAAEAABCSHu6lz4vgk5G3E32OFcIPEZZgdOEYE/
+Content-Type: application/xml
+Date: Wed, 27 Jun 2018 13:42:39 GMT
+Content-Length: 337
+
+<?xml version="1.0" encoding="utf-8"?>
+<ReplicationConfiguration xmlns="http://obs.example.com/doc/2006-03-01/">
+ <Rule>
+ <ID>Rule-1</ID>
+ <Status>Enabled</Status>
+ <Prefix></Prefix>
+ <Destination>
+ <Bucket>dstbucket</Bucket>
+ <StorageClass>STANDARD</StorageClass>
+ <DeleteData>Enabled</DeleteData>
+ </Destination>
+ <HistoricalObjectReplication>Enabled</HistoricalObjectReplication>
+ </Rule>
+ <Agency>testAcy</Agency>
+</ReplicationConfiguration>
+ |
+
+
+
+
+
+
diff --git a/docs/obs/api-ref/obs_04_0048.html b/docs/obs/api-ref/obs_04_0048.html
new file mode 100644
index 000000000..c3f4cdfa8
--- /dev/null
+++ b/docs/obs/api-ref/obs_04_0048.html
@@ -0,0 +1,74 @@
+
+
+ Deleting the Cross-Region Replication Configuration of a Bucket
+ FunctionsYou can perform this operation to delete the bucket replication configuration. To perform this operation, you must have the DeleteReplicationConfiguration permission.
+
+ Request Syntax | DELETE /?replication HTTP/1.1
+Host: bucketname.obs.region.example.com
+Date: date
+Authorization: authorization string
+ |
+
+
+
+ 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 Syntax | HTTP/1.1 204 No Content
+Server: OBS
+Date: date
+Connection: keep-alive
+ |
+
+
+
+ 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 this request.
+
+ Sample Request | DELETE /?replication HTTP/1.1
+User-Agent: curl/7.29.0
+Host: examplebucket.obs.region.example.com
+Accept: */*
+Date: Wed, 27 Jun 2018 13:45:50 GMT
+Authorization: OBS H4IPJX0TQTHTHEBQQCEC:3ycNYD0CfMf0gOmmXzdGJ58KjHU=
+ |
+
+
+
+ Sample Response | HTTP/1.1 204 No Content
+Server: OBS
+x-obs-request-id: 900B000001643FE6BBCC9C9F54FA7A7E
+x-obs-id-2: 32AAAQAAEAABSAAgAAEAABAAAQAAEAABCS8Exs52zCf9duxPLnBircmGa/JOCjec
+Date: Wed, 27 Jun 2018 13:45:50 GMT
+ |
+
+
+
+
+
+
diff --git a/docs/obs/api-ref/obs_04_0080.html b/docs/obs/api-ref/obs_04_0080.html
index 3d38e30c3..8cc3dbaf4 100644
--- a/docs/obs/api-ref/obs_04_0080.html
+++ b/docs/obs/api-ref/obs_04_0080.html
@@ -8,7 +8,7 @@
You can also specify the value of the x-obs-acl parameter to configure an access control policy for the object. If the x-obs-acl parameter is not specified when an anonymous user uploads an object, the object can be accessed by all OBS users by default.
This operation supports server-side encryption.
For a single upload, the size of the object to be uploaded ranges [0, 5 GB]. To upload a file greater than 5 GB, see Operations on Multipart Upload.
- OBS does not have real folders. To facilitate data management, OBS provides a method to simulate a folder by adding a slash (/) to the object name, for example, test/123.jpg. You can simulate test as a folder and 123.jpg as the name of a file under the test folder. However, the object key remains test/123.jpg. Objects named in this format appear as folders on the console.
+ OBS does not have real folders. To facilitate data management, OBS provides a method to simulate a folder by adding a slash (/) to the object name, for example, test/123.jpg. You can simulate test as a folder and 123.jpg as the name of a file under the test folder. However, the object key remains test/123.jpg. Objects named in this format appear as folders on the console. When you upload an object larger than 0 in size using this format, an empty folder will be displayed on the console, but the occupied storage capacity is the actual object size.
Differences Between PUT and POST MethodsParameters are passed through the request header if the PUT method is used to upload objects; if the POST method is used to upload objects, parameters are passed through the form field in the message body.
With the PUT method, you need to specify the object name in the URL, but object name is not required with the POST method, which uses the bucket domain name as the URL. The request lines of the two methods are as follows:
@@ -196,7 +196,7 @@ Date: date
success-action-redirect
|
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 is invalid, OBS ignores this parameter. The response code is 204, and the Location is the object address.
+- 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
|
No
@@ -230,7 +230,7 @@ Content-Type: type
Response HeadersThe response to the request uses common headers. For details, see Table 1.
In addition to the common response headers, the following message headers may also be used. For details, see Table 2.
- Table 2 Additional response header parametersHeader
+Table 2 Additional response headersHeader
|
Description
|
diff --git a/docs/obs/api-ref/obs_04_0081.html b/docs/obs/api-ref/obs_04_0081.html
index 81903fc85..ec06ee17b 100644
--- a/docs/obs/api-ref/obs_04_0081.html
+++ b/docs/obs/api-ref/obs_04_0081.html
@@ -312,7 +312,7 @@ Upload to OBS success_action_redirect
|
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 is invalid, OBS ignores this parameter. The response code is 204, and the Location is the object address.
+- 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:
In POLICY: {"success_action_redirect": "http://123458.com"},
@@ -436,7 +436,7 @@ ETag: etag
Response HeadersThe response to the request uses common headers. For details, see Table 1.
In addition to the common response headers, the following message headers may also be used. For details, see Table 3.
- Table 3 Additional response header parametersHeader
+Table 3 Additional response headersHeader
|
Description
|
diff --git a/docs/obs/api-ref/obs_04_0082.html b/docs/obs/api-ref/obs_04_0082.html
index 823ab9c77..e9b407154 100644
--- a/docs/obs/api-ref/obs_04_0082.html
+++ b/docs/obs/api-ref/obs_04_0082.html
@@ -260,7 +260,7 @@ Date: date
|---|
success_action_redirect
|
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 is invalid, OBS ignores this parameter. The response code is 204, and the Location is the object address.
+- 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
|
No
@@ -299,7 +299,7 @@ Content-Length: length
Response HeadersThe response to the request uses common headers. For details, see Table 1.
In addition to the common response headers, the following message headers may also be used. For details, see Table 2.
- Table 2 Additional response header parametersHeader
+Table 2 Additional response headersHeader
|
Description
|
diff --git a/docs/obs/api-ref/obs_04_0084.html b/docs/obs/api-ref/obs_04_0084.html
index e08b3347e..61290d615 100644
--- a/docs/obs/api-ref/obs_04_0084.html
+++ b/docs/obs/api-ref/obs_04_0084.html
@@ -120,7 +120,7 @@ Last-Modified: time
Response HeadersThe response to the request uses common headers. For details, see Table 1.
In addition to the common response headers, the following message headers may also be used. For details, see Table 3.
- Table 3 Additional response header parametersHeader
+Table 3 Additional response headersHeader
|
Description
|
@@ -213,7 +213,7 @@ Last-Modified: time
|---|
x-obs-restore
|
-This header is returned when a Cold object is being restored or has been restored. It represents the object's restore status, which can be ongoing-request="true" (the object is being restored) or ongoing-request="false", expiry-date="Wed, 07 Nov 2012 00:00:00 GMT" (the object has been restored). In these statuses, expiry-date indicates when the restored object will expire.
+ | This header is returned when a Cold object is being restored or has been restored. It represents the object's restore status, which can be ongoing-request="true" (the object is being restored) or ongoing-request="false", expiry-date="Wed, 7 Nov 2012 00:00:00 GMT" (the object has been restored). In these statuses, expiry-date indicates when the restored object will expire.
Type: string
|
diff --git a/docs/obs/api-ref/obs_04_0085.html b/docs/obs/api-ref/obs_04_0085.html
index 4432ed21a..27c14cda9 100644
--- a/docs/obs/api-ref/obs_04_0085.html
+++ b/docs/obs/api-ref/obs_04_0085.html
@@ -53,9 +53,9 @@ Date: date
Response HeadersThe response to the request uses common headers. For details, see Table 1.
- In addition to the common response headers, the following message headers may also be used. For details, see Table 2.
+ If versioning is enabled for the bucket, the headers listed in Table 2 may also be used.
- Table 2 Additional response header parametersHeader
+Table 2 Additional response headersHeader
|
Description
|
@@ -73,7 +73,7 @@ Date: date
Object version ID. If the object has no version number specified, the response does not contain this header.
Valid value: character string
-There is no default value.
+Default value: none
|
|---|
diff --git a/docs/obs/api-ref/obs_04_0087.html b/docs/obs/api-ref/obs_04_0087.html
index c75b02171..b39e47113 100644
--- a/docs/obs/api-ref/obs_04_0087.html
+++ b/docs/obs/api-ref/obs_04_0087.html
@@ -77,8 +77,8 @@ Content-MD5: MD5
Tier
|
Restore options: Expedited | Standard
-Expedited indicates that objects can be quickly restored within 1 to 5 minutes from Archive storage and within 3 to 5 hours from Deep Archive storage.
-Standard indicates that objects can be restored within 3 to 5 hours from Archive storage and within 5 to 12 hours from Deep Archive storage.
+Expedited indicates that objects can be quickly restored from Archive storage within 1 to 5 minutes.
+Standard indicates that objects can be restored from Archive storage within 3 to 5 hours.
The default value is Standard.
Type: string
|
diff --git a/docs/obs/api-ref/obs_04_0102.html b/docs/obs/api-ref/obs_04_0102.html
index 59c7035d3..5376d0dca 100644
--- a/docs/obs/api-ref/obs_04_0102.html
+++ b/docs/obs/api-ref/obs_04_0102.html
@@ -139,7 +139,7 @@ Date: date
Response HeadersThe response to the request uses common headers. For details, see Table 1.
In addition to the common response headers, the following message headers may also be used. For details, see Table 3.
- Table 3 Additional response header parametersHeader
+Table 3 Additional response headersHeader
|
Description
|
diff --git a/docs/obs/api-ref/obs_04_0114.html b/docs/obs/api-ref/obs_04_0114.html
index 6d764a14f..767bcba44 100644
--- a/docs/obs/api-ref/obs_04_0114.html
+++ b/docs/obs/api-ref/obs_04_0114.html
@@ -27,6 +27,8 @@
|---|
Send API requests using the HTTP/HTTPS format that complies with https://www.ietf.org/rfc/rfc2616.txt.
+
diff --git a/docs/obs/api-ref/obs_04_0115.html b/docs/obs/api-ref/obs_04_0115.html
index 21a0d8fd5..afc4e3afe 100644
--- a/docs/obs/api-ref/obs_04_0115.html
+++ b/docs/obs/api-ref/obs_04_0115.html
@@ -160,18 +160,19 @@ QUFBQUFBYmJiYmJiYmJD </HostId>
EntityTooLarge
|
- The size of the object uploaded using the POST method exceeds the upper limit.
+ | - The size of the file uploaded using the PUT, POST, or Append methods of SDKs or APIs exceeds 5 GB.
- The part uploaded is larger than 5 GB in size.
- The size of the bucket configurations exceeds 20 KB.
- The file size exceeds the upper limit defined in the policy of the POST form.
+- The size of the file uploaded using the multipart upload of SDKs or APIs or the resumable upload of SDKs exceeds 48.8 TB.
|
- Modify the conditions specified in the policy when posting the object or reduce the object size.
+ | Modify the conditions specified in the upload policy or reduce the object size.
|
|
|---|
400 Bad Request
|
EntityTooSmall
|
-The size of the object uploaded using the POST method does not reach the lower limit.
+ | - The part uploaded, except the last one, is smaller than 100 KB.
- The file size is smaller than the lower limit defined in the policy of the POST form.
|
-Modify the conditions specified in the policy when posting the object or increase the object size.
+ | Modify the conditions specified in the upload policy or increase the object size.
|
400 Bad Request
@@ -228,6 +229,24 @@ QUFBQUFBYmJiYmJiYmJD</HostId> Change the bucket name.
|
+400 Bad Request
+ |
+InvalidContentLength
+ |
+Invalid Content-Length value.
+ |
+Check the encapsulation header or contact technical support.
+ |
+
+400 Bad Request
+ |
+InvalidDefaultStorageClass
+ |
+The default storage class is invalid.
+ |
+Check which storage classes can be used.
+ |
+
400 Bad Request
|
InvalidEncryptionAlgorithmError
@@ -444,6 +463,15 @@ QUFBQUFBYmJiYmJiYmJD</HostId> Provide required headers.
|
+400 Bad Request
+ |
+MultipleContentLengths
+ |
+There are multiple Content-Length headers.
+ |
+Check the encapsulation header or contact technical support.
+ |
+
400 Bad Request
|
TooManyBuckets
| |
|---|
|
|---|
|---|
|
|---|
| |
|---|
|
|---|
|
|---|
| | |