upload method
Uploads an object and its metadata to Object Storage.
Note
Object Storage doesn't block objects for writing and can accept multiple requests to write to the same object in parallel, but the user can only get the latest object saved from Object Storage by default. To ensure that the history is saved when objects are overwritten or deleted, enable versioning.
To make sure an object is passed via the network without any corruption, use the Content-MD5
header. Object Storage calculates the MD5
value for a saved object and, if the calculated MD5
value does not match the one passed in the header, it returns an error. You can also perform this check on the client side by comparing the ETag
from the Object Storage response with the precalculated MD5
value.
Request
PUT /{bucket}/{key} HTTP/2
Path parameters
Parameter | Description |
---|---|
bucket |
Bucket name. |
key |
Object key. ID for saving the object in Object Storage. |
Headers
Use the necessary common request headers in requests.
You can also use the headers listed in the table below.
Header | Description |
---|---|
X-Amz-Meta-* |
User-defined metadata. Object Storage transforms all headers starting with X-Amz-Meta- as follows: X-Amz-Meta-foo-bar_baz → X-Amz-Meta-Foo-Bar_baz .Total user-defined header size must not exceed 2 KB. The size of user-defined data is determined as the length of the UTF-8 encoded string. The header names and their values are included when calculating the size. |
Response
Headers
Responses can only contain common response headers.
Response codes
For a list of possible responses, see Responses.