PostContainer
- Print
- PDF
PostContainer
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Available in Classic and VPC
Set or change metadata on a container (bucket).
Requests
The following describes the request format for the endpoint. The request format is as follows.
| Method | URI |
|---|---|
| POST | /{containerName} |
Request headers
The following describes the headers.
| Field | Type | Required | Description |
|---|---|---|---|
x-ncp-apigw-timestamp | String | Required | Timestamp value
|
x-ncp-iam-access-key | String | Required | API key issued by NAVER Cloud Platform or access key issued by Sub Account |
x-ncp-apigw-signature-v2 | String | Required | Signature used to encrypt the body of the above example with the secret key that maps with the access key ID
|
x-ncp-region_code | String | Required | Region code of the container
|
X-Container-Meta-Access-Control-Allow-Origin | String | Optional | CORS setting
|
X-Container-Meta-Access-Control-Max-Age | String | Optional | CORS setting
|
X-Container-Meta-Access-Control-Expose-Headers | String | Optional | CORS setting
|
Request path parameters
The following describes the parameters.
| Field | Type | Required | Description |
|---|---|---|---|
containerName | String | Required | Name of the container (bucket) to set or edit |
Request example
The following is a sample request.
curl -X POST "https://archivestorage.apigw.ntruss.com/swift/v1/{containerName}" -H "accept: application/json" -H "X-Container-Meta-Access-Control-Allow-Origin: http://localhost" -H "x-ncp-region-code: {regionCode}"
-H "x-ncp-iam-access-key: {AccessKey} "
-H "x-ncp-apigw-timestamp: {current timestamp}"
-H "x-ncp-apigw-signature-v2: {generated signature}"
Responses
The following describes the response format.
Response headers
The following describes the headers.
| Field | Type | Required | Description |
|---|---|---|---|
Server | String | - | Response server |
Date | String | - | Response time of the request (UTC) |
Connection | String | - | TCP connection status between client and server |
X-Storage-Policy | Integer | - | Storage policy value for the container |
X-Timestamp | Integer | - | Creation time of the container (Unix timestamp) |
X-Container-Bytes-Used | Integer | - | Amount of capacity the container is using |
X-Trans-Id | String | - | Transaction ID of the request |
X-Openstack-Request-Id | String | - | Transaction ID of the request
|
X-Container-Object-Count | Integer | - | Number of objects stored in the container |
X-Container-Meta-Access-Control-Allow-Origin | String | - | CORS settings
|
Referrer-Policy | String | - | HTTP Referrer header handling method |
x-ncp-apigw-response-origin | String | - | Original source of the response |
x-ncp-trace-id | String | - | ID for transaction tracking |
Response example
The following is a sample response.
HTTP/1.1 204 No Content
Server: nginx
Date: Tue, 16 Apr 2024 01:56:58 GMT
Connection: keep-alive
X-Storage-Policy: standard00
X-Timestamp: 1711960998.26335
X-Container-Bytes-Used: 0
X-Openstack-Request-Id: txf770951820a44a91bc450-00661de4f8
X-Container-Object-Count: 0
X-Container-Meta-Access-Control-Allow-Origin: http://localhost
X-Trans-Id: txf770951820a44a91bc450-00661de4f8
Referrer-Policy: unsafe-url
x-ncp-trace-id: 6cd9l6lj66d356cchgc4rjcc1o
x-ncp-apigw-response-origin: ENDPOINT
Was this article helpful?