The table below describes the headers you can use in a request to add an ACL container.
Name | Type | Description |
---|---|---|
X-Auth-Token | String (Required) | See, Common request headers |
X-Container-Meta-Quota-Bytes | String | Sets a limit on the size, in bytes, of objects that can be stored in the container. |
X-Container-Read | String |
Adds a Read, Browse or both access permissions to the container. This header can be used to add permissions to individual Keystone users or make the container public. For valid values for this header, see Setting ACL permissions |
X-Container-Write | String |
Adds Write, Delete or both access permissions to the container. This header can be used to add permissions to individual Keystone users or make the container public. For valid values for this header, see Setting ACL permissions. |
X-Remove-Container-name | String |
This header removes other headers supported by the POST command. Instead of replacing the data with new information, this header acts as a delete for other headers. Here is an example of how to use the header. If you want to get rid of all your X-Container-Write ACL permissions on a container you format the X-Remove-Container-name header like this: X-Remove-Container-Write When you execute this example operation all write ACLs are removed from the container. |
© 2017 Hitachi Data Systems Corporation. All rights reserved.