-
Cache-Control
-
Content-Disposition
-
Content-Encoding
-
Content-Length
-
Content-MD5
-
Content-Type
-
Expect
-
Expires
-
x-amz-meta-
-
x-amz-storage-class
-
x-amz-website-redirect-location
-
x-amz-acl
-
x-amz-grant-read
-
x-amz-grant-write
-
x-amz-grant-read-acp
-
x-amz-grant-write-acp
-
x-amz-grant-full-control
-
x-amz-server-side-encryption
Vault Extension to the S3 API
The Vault system supports the following Request Header as an extension to the "PUT Object" operation:
|
Name |
Description |
Required |
|---|---|---|
|
x-gmt-hyperstore |
Clients can use this header to specify the Vault storage type to apply to the object that’s being PUT. Options are:
|
No |
Vault Restrictions on Object Names
The following control characters cannot be used anywhere in an object name and will result in a 400 Bad Request response: 0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A ("\n"), 0x0B, 0x0C, 0x0D ("\r"), 0x0E, 0x0F, 0x10, 0x11, 0x12, 0x13, 0x14, 0x15, 0x16, 0x17, 0x18, 0x19, 0x1A, 0x1B, 0x1C, 0x1D, 0x1E, 0x1F
Also unsupported are:
-
0x09 ("\t") at the beginning of an object name
-
0xBF (inverted question mark) at the end of an object name
Also, an object name may result in 400 Bad Request or be stored as a different name if the supplied object name:
-
Consists only of "."
-
Consists only of ".."
-
Contains a combination of "." and "/", or ".." and "/"
Examples of character sequences that will result in 400 Bad Request:
|
. |
|
.. |
|
./ |
|
../ |
|
./. |
|
./.. |
|
../. |
|
../.. |
|
../a |
|
../a/ |
|
a/../../b |
Examples of character sequences that will be stored as a different name:
| Supplied Object Name | Stored As |
|---|---|
|
./a |
a |
|
./a/ |
a/ |
|
a//b |
a/b |
|
a/./b |
a/b |
|
a/../b |
b |
|
a/.././b |
b |