Storing object request contents

The PUT request to store an object or version has these elements:

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

A URL specifying the location in which to store the object

A body containing the fixed-content data to be stored in the namespace

Conditionally storing a version

To store a version of an existing object only if the object meets certain conditions, use the headers listed in Conditional operations.

Storing object data and custom metadata together

You can use a single request to store object data and a single annotation. To do this, the request body must contain the fixed-content data to be stored, followed by the annotation content, with no delimiter between them.

Additionally, specify these request elements:

A type URL query parameter with a value of whole-object.

An X-HCP-Size header specifying the size, in bytes, of the object data.

For all annotations except the default annotation, an annotation URL query parameter with a value of the name of the annotation. For the default annotation, the annotation URL is optional.

When you store object data and an annotation in a single operation, the object data must always precede the custom metadata. This differs from the behavior when you retrieve the object data together with the an annotation, where you can tell HCP to return the results in either order.

Sending data in compressed format

You can send the request body in compressed format and have HCP decompress it 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.

Trademark and LegalDisclaimer

© 2015 Hitachi Data Systems Corporation. All rights reserved.