Supported Common Request Headers

Language:

The following table identifies the common request headers supported by the Oracle ZFS Storage Appliance S3 Object API Service.

Table 7 Common Supported Request Headers

Supported Request Header	Description	Required
Authorization	The Authorization header field identifies the information required for request signature authentication. For more information, see "The Authentication Header" in the Amazon Simple Storage Service Developer Guide (https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-dg.pdf).	Yes Note - For anonymous requests, this header is not required
Content-Length	The Content-Length header field represents the length of the message (without the headers) according to RFC 2616.	No Note - This header is required for PUTs and load XML operations
Content-MD5	The Content-MD5 header field represents the base64 encoded 128-bit MD5 digest of the message (without the headers) according to RFC 1864. This header is used as a message integrity check to verify that the data is the same data that was originally sent.	No
Date -or- x-amz-date	These header fields represents the current date and time according to the requester. When you specify the Authorization header, you must specify either the `x-amz-date` or the `Date` header. If you specify both, the value specified for the `x-amz-date` header takes precedence	Yes.
Expect	The Expect header field is used only when sending a request body with the property values: 100-continue. Note - When your application uses 100-continue as a property value, the request body is not sent until after it receives an acknowledgment. If the message is rejected based on the headers, the body of the message is not sent.	No
Host	The Oracle ZFS Storage Appliance Host FQDNT header field is required for HTTP 1.1 (most toolkits add this header automatically); optional for HTTP/1.0 requests.	Yes
x-amz-content-sha256	When using signature version 4 to authenticate a request, the x-amz-content-sha256 header field provides a hash of the request payload. For more information, see Amazon's official documentation for Signature Calculations for the Authorization Header: Transferring Payload in a Single Chunk (AWS Signature Version 4). When uploading an object in chunks, you can set the value to STREAMING-AWS4-HMAC-SHA256-PAYLOAD to indicate that the signature covers only headers and that there is no payload. For more information, see Amazon's official documentation for Signature Calculations for the Authorization Header: Transferring Payload in Multiple Chunks (Chunked Upload) (AWS Signature Version 4) .	Yes