PUT Object
PUT {{baseUrl}}/n/:namespaceName/b/:bucketName/o/:objectName
Creates a new object or overwrites an existing object with the same name. The maximum object size allowed by PutObject is 50 GiB.
See Object Names for object naming requirements.
See Special Instructions for Object Storage PUT for request signature requirements.
HEADERS
| Key | Datatype | Required | Description |
|---|---|---|---|
if-match | string | The entity tag (ETag) to match with the ETag of an existing resource. If the specified ETag matches the ETag of | |
| the existing resource, GET and HEAD requests will return the resource and PUT and POST requests will upload | |||
| the resource. | |||
if-none-match | string | The entity tag (ETag) to avoid matching. The only valid value is '*', which indicates that the request should | |
| fail if the resource already exists. | |||
opc-client-request-id | string | The client request ID for tracing. | |
Expect | null | A value of 100-continue requests preliminary verification of the request method, path, and headers before the request body is sent. | |
| If no error results from such verification, the server will send a 100 (Continue) interim response to indicate readiness for the request body. | |||
| The only allowed value for this parameter is "100-Continue" (case-insensitive). | |||
Content-Length | number | (Required) The content length of the body. | |
Content-MD5 | string | The optional base-64 header that defines the encoded MD5 hash of the body. If the optional Content-MD5 header is present, Object | |
| Storage performs an integrity check on the body of the HTTP request by computing the MD5 hash for the body and comparing it to the | |||
| MD5 hash supplied in the header. If the two hashes do not match, the object is rejected and an HTTP-400 Unmatched Content MD5 error | |||
| is returned with the message: |
"The computed MD5 of the request body (ACTUAL_MD5) does not match the Content-MD5 header (HEADER_MD5)"
|
| Content-Language | string | | The optional Content-Language header that defines the content language of the object to upload. Specifying
values for this header has no effect on Object Storage behavior. Programs that read the object determine what
to do based on the value provided. For example, you could use this header to identify and differentiate objects
based on a particular language.
|
| Content-Encoding | string | | The optional Content-Encoding header that defines the content encodings that were applied to the object to
upload. Specifying values for this header has no effect on Object Storage behavior. Programs that read the
object determine what to do based on the value provided. For example, you could use this header to determine
what decoding mechanisms need to be applied to obtain the media-type specified by the Content-Type header of
the object.
|
| Content-Disposition | string | | The optional Content-Disposition header that defines presentational information for the object to be
returned in GetObject and HeadObject responses. Specifying values for this header has no effect on Object
Storage behavior. Programs that read the object determine what to do based on the value provided.
For example, you could use this header to let users download objects with custom filenames in a browser.
|
| Cache-Control | string | | The optional Cache-Control header that defines the caching behavior value to be returned in GetObject and
HeadObject responses. Specifying values for this header has no effect on Object Storage behavior. Programs
that read the object determine what to do based on the value provided.
For example, you could use this header to identify objects that require caching restrictions.
|
| opc-sse-customer-algorithm | string | | The optional header that specifies "AES256" as the encryption algorithm. For more information, see
Using Your Own Keys for Server-Side Encryption.
|
| opc-sse-customer-key | string | | The optional header that specifies the base64-encoded 256-bit encryption key to use to encrypt or
decrypt the data. For more information, see
Using Your Own Keys for Server-Side Encryption.
|
| opc-sse-customer-key-sha256 | string | | The optional header that specifies the base64-encoded SHA256 hash of the encryption key. This
value is used to check the integrity of the encryption key. For more information, see
Using Your Own Keys for Server-Side Encryption.
|
| opc-sse-kms-key-id | string | | The OCID of a master encryption key used to call the Key
Management service to generate a data encryption key or to encrypt or decrypt a data encryption key.
|
| storage-tier | string | | The storage tier that the object should be stored in. If not specified, the object will be stored in
the same storage tier as the bucket.
|
| opc-meta-* | string | | Optional user-defined metadata key and value. |
| Content-Type | string | | |
| Accept | string | | |
RESPONSES
status: OK
""