Object operations

The following Swift API operations are performed on objects.

DELETE object

This operation deletes an object's content and metadata from the StorageGRID Webscale system.

The following request parameters are required:

Account
Container
Object

The following request header is required:

X-Auth-Token

A successful execution returns the following response headers with an "HTTP/1.1 204 No Content" response:

Content-Length
Content-Type
Date
X-Trans-Id

GET object

This operation retrieves the object content and gets the object metadata from a StorageGRID Webscale system.

The following request parameters are required:

Account
Container
Object

The following request header is required:

X-Auth-Token

The following request headers are optional:

Accept-Encoding
If-Match
If-Modified-Since
If-None-Match
If-Unmodified-Since
Range

A successful execution returns the following headers with an "HTTP/1.1 200 OK" response:

Accept-Ranges
Content-Length
Content-Type
Date
ETag
Last-Modified
X-Timestamp
X-Trans-Id

HEAD object

This operation retrieves metadata and properties of an ingested object from a StorageGRID Webscale system.

The following request parameters are required:

Account
Container
Object

The following request header is required:

X-Auth-Token

A successful execution returns the following headers with an "HTTP/1.1 200 OK" response:

Accept-Ranges
Content-Length
Content-Type
Date
ETag
Last-Modified
X-Timestamp
X-Trans-Id

PUT object

This operation creates a new object with data and metadata, or replaces an existing object with data and metadata in a StorageGRID Webscale system.

Note: StorageGRID Webscale supports objects up to 5 TB in size.

Attention: Conflicting client requests, such as a two clients writing to the same key, are resolved on a "latest-wins" basis. The timing for the "latest-wins" evaluation is based on when the StorageGRID Webscale system completes a given request, and not on when Swift clients begin an operation.

The following request parameters are required:

Account
Container
Object

The following request header is required:

X-Auth-Token

The following request headers are optional:

Content-Encoding
Content-Length
Content-Type
ETag
Transfer-Encoding
X-Object-Meta-<name> (object-related metadata)
If you want to use the User Defined Creation Time option as the Reference Time for an ILM rule, you must store the value in a user-defined header named X-Object-Meta-Creation-Time. For example:
```
X-Object-Meta-Creation-Time: 1443399726
```
This field is evaluated as seconds since January 1, 1970.
X-Storage-Class: reduced_redundancy
Specifies a single-commit ingest operation. Use this header to specify reduced_redundancy only if you need to limit redundant storage at the time of ingest and only if you are willing to risk the loss of object data. For example, you might lose data if the single copy is initially stored on a Storage Node that fails before ILM evaluation can occur.

Specifying reduced_redundancy only affects how many copies are created when an object is first ingested. It does not affect how many copies of the object are made when the object is evaluated by the active ILM policy. Using reduced_redundancy does not result in data being stored at lower levels of redundancy in the StorageGRID Webscale system.

A successful execution returns the following headers with an "HTTP/1.1 201 Created" response:

Content-Length
Content-Type
Date
ETag
Last-Modified
X-Trans-Id