5 A container is a mechanism for storing data objects. An account may
6 have many containers, but container names must be unique. This API enables a
7 client to create a container, set access controls and metadata,
8 retrieve a container's contents, and delete a container. Since this API
9 makes requests related to information in a particular user's account, all
10 requests in this API must be authenticated unless a container's access control
11 is deliberately made publicly accessible (i.e., allows anonymous requests).
13 .. note:: The Amazon S3 API uses the term 'bucket' to describe a data container.
14 When you hear someone refer to a 'bucket' within the Swift API, the term
15 'bucket' may be construed as the equivalent of the term 'container.'
17 One facet of object storage is that it does not support hierarchical paths
18 or directories. Instead, it supports one level consisting of one or more
19 containers, where each container may have objects. The RADOS Gateway's
20 Swift-compatible API supports the notion of 'pseudo-hierarchical containers,'
21 which is a means of using object naming to emulate a container (or directory)
22 hierarchy without actually implementing one in the storage system. You may
23 name objects with pseudo-hierarchical names
24 (e.g., photos/buildings/empire-state.jpg), but container names cannot
25 contain a forward slash (``/``) character.
31 To create a new container, make a ``PUT`` request with the API version, account,
32 and the name of the new container. The container name must be unique, must not
33 contain a forward-slash (/) character, and should be less than 256 bytes. You
34 may include access control headers and metadata headers in the request. The
35 operation is idempotent; that is, if you make a request to create a container
36 that already exists, it will return with a HTTP 202 return code, but will not
37 create another container.
45 PUT /{api version}/{account}/{container} HTTP/1.1
47 X-Auth-Token: {auth-token}
48 X-Container-Read: {comma-separated-uids}
49 X-Container-Write: {comma-separated-uids}
50 X-Container-Meta-{key}: {value}
58 :Description: The user IDs with read permissions for the container.
59 :Type: Comma-separated string values of user IDs.
64 :Description: The user IDs with write permissions for the container.
65 :Type: Comma-separated string values of user IDs.
68 ``X-Container-Meta-{key}``
70 :Description: A user-defined meta data key that takes an arbitrary string value.
78 If a container with the same name already exists, and the user is the
79 container owner then the operation will succeed. Otherwise the operation
84 :Description: The container already exists under a different user's ownership.
85 :Status Code: ``BucketAlreadyExists``
90 List a Container's Objects
91 ==========================
93 To list the objects within a container, make a ``GET`` request with the with the
94 API version, account, and the name of the container. You can specify query
95 parameters to filter the full list, or leave out the parameters to return a list
96 of the first 10,000 object names stored in the container.
104 GET /{api version}/{container} HTTP/1.1
106 X-Auth-Token: {auth-token}
114 :Description: Defines the format of the result.
116 :Valid Values: ``json`` | ``xml``
121 :Description: Limits the result set to objects beginning with the specified prefix.
127 :Description: Returns a list of results greater than the marker value.
133 :Description: Limits the number of results to the specified value.
135 :Valid Range: 0 - 10,000
140 :Description: The delimiter between the prefix and the rest of the object name.
146 :Description: The pseudo-hierarchical path of the objects.
156 :Description: The container.
161 :Description: An object within the container.
166 :Description: The name of an object within the container.
171 :Description: A hash code of the object's contents.
176 :Description: The last time the object's contents were modified.
181 :Description: The type of content within the object.
186 Update a Container's ACLs
187 =========================
189 When a user creates a container, the user has read and write access to the
190 container by default. To allow other users to read a container's contents or
191 write to a container, you must specifically enable the user.
192 You may also specify ``*`` in the ``X-Container-Read`` or ``X-Container-Write``
193 settings, which effectively enables all users to either read from or write
194 to the container. Setting ``*`` makes the container public. That is it
195 enables anonymous users to either read from or write to the container.
203 POST /{api version}/{account}/{container} HTTP/1.1
205 X-Auth-Token: {auth-token}
207 X-Container-Write: {uid1}, {uid2}, {uid3}
214 :Description: The user IDs with read permissions for the container.
215 :Type: Comma-separated string values of user IDs.
218 ``X-Container-Write``
220 :Description: The user IDs with write permissions for the container.
221 :Type: Comma-separated string values of user IDs.
225 Add/Update Container Metadata
226 =============================
228 To add metadata to a container, make a ``POST`` request with the API version,
229 account, and container name. You must have write permissions on the
230 container to add or update metadata.
237 POST /{api version}/{account}/{container} HTTP/1.1
239 X-Auth-Token: {auth-token}
240 X-Container-Meta-Color: red
241 X-Container-Meta-Taste: salty
246 ``X-Container-Meta-{key}``
248 :Description: A user-defined meta data key that takes an arbitrary string value.
257 To delete a container, make a ``DELETE`` request with the API version, account,
258 and the name of the container. The container must be empty. If you'd like to check
259 if the container is empty, execute a ``HEAD`` request against the container. Once
260 you've successfully removed the container, you'll be able to reuse the container name.
267 DELETE /{api version}/{account}/{container} HTTP/1.1
269 X-Auth-Token: {auth-token}
277 :Description: The container was removed.
278 :Status Code: ``NoContent``