Storing an ACL request contents

The PUT request to store an ACL has these elements:

If you’re accessing the namespace as an authenticated user, an Authorization header.

A URL specifying the object for which you’re adding the ACL.

A type=acl URL query parameter.

A body consisting of the ACL XML or JSON. For information on the elements that you specify in an ACL body, see ACL body.

To specify the format of the ACL data, optionally, an HTTP Content-Type header with one of these values:

oIf the ACL body is XML, application/xml

oIf the ACL body is JSON, application/json

The default is application/xml.

Sending data in compressed format

You can send an ACL in compressed format and have HCP decompress the ACL before storing it. To do this:

Use gzip to compress the content before sending it.

Include a Content-Encoding request header with a value of gzip.

Use a chunked transfer encoding.

Storing a predefined ACL

HCP has two predefined ACLs that you can specify when storing a new object:

all_read — Grants read permission for the object to all users

auth_read — Grants read permission for the object to all authenticated users

For information on specifying a predefined ACL for a new object, see Specifying metadata on object creation.

Trademark and LegalDisclaimer

© 2015 Hitachi Data Systems Corporation. All rights reserved.