Common request headers

Some request headers are common to all S3 compatible API requests. The table below describes those headers. Request headers that are specific to certain requests are described in the sections for those requests in Working with buckets, Working with objects, and Working with multipart uploads.

Request header names are not case sensitive. Depending on the header, the header values may be case sensitive.

Request header Description
Authorization Specifies user credentials or requests anonymous access. For valid values for this header, see Authentication.
Date

Specifies the date and time when the request is being made according to the requester. Normally, this is the current date and time.

The date and time must always be specified using Greenwich Mean Time (GMT).

To specify the date and time, use this format:

DDD, dd MMM yyyy HH:mm:ss (+0000|GMT)

In this format:

DDD is the three-letter abbreviation for the day of the week, with an uppercase first letter (for example, Mon).

dd is the two-digit day of the month.

MMM is the three-letter abbreviation for the month, with an uppercase first letter (for example, Feb).

yyyy is the four-digit year.

HH is the hour on a 24-hour clock.

mm is the number of minutes.

ss is the number of seconds.

For example:

Thu, 23 Mar 2017 14:27:05 +0000

All S3 compatible requests must include either a Date header or an x-amz-date header. If a request includes both headers, HCP uses the date and time in the x-amz-date header.

Host

Specifies the hostname for the request. The host name identifies either a tenant or a bucket.

For a tenant, use this format:

tenant-name.hcp-domain-name

For a bucket, use this format:

bucket-name.tenant-name.hcp-domain-name

x-amz-date

Specifies the date and time at which the request is being made according to the requester. Normally, this is the current date and time.

For the valid values for this header, see the description of the Date header above.

Note: HCP accepts but does not process several standard HTTP request headers. Among others, these include Cache-Control, Connection, Content-Disposition, Content-Encoding, Content-Language, and Pragma. For more information about HTTP request headers, see the HTTP/1.1 standards (RFCs 7230 through 7237).

© 2015, 2020 Hitachi Vantara LLC. All rights reserved.