Gateway performs translations of custom metadata formatting between the S3 and SCSP protocols as of release 5.4. Gateway now provides S3 and SCSP applications the ability to access each other's metadata.
Gateway provides the following translations for Custom Metadata Headers to allow SCSP and S3 clients to manipulate the full set of metadata Swarm Storage supports:
SCSP | S3 | |||||
|---|---|---|---|---|---|---|
| <- both ways -> |
| ||||
| <- both ways -> |
| ||||
| one way only -> |
|
S3 Client Issues
In an S3 client (e.g. Cyberduck object Info => Metadata tab) add two custom metadata values ("meta = cyberduck1" and "amz-meta = cyberduck2") as follows:
x-amz-meta-meta: cyberduck1
x-amz-meta-amz-meta: cyberduck2
Gateway merges to the same header name because occurrences of "amz-meta-" are removed when stored in Swarm. Here is how that custom metadata is returned in SCSP and S3:
SCSP HEAD
| Code Block | ||
|---|---|---|
| ||
curl --head -u caringoadmin:password 'http://mydomain.example.com:9984/mybucket/duck.mpeg' ... x-meta-meta: cyberduck1 x-meta-meta: cyberduck2 ... |
S3 HEAD
| Code Block | ||
|---|---|---|
| ||
curl --head -u caringoadmin:password 'http://mydomain.example.com:9985/mybucket/duck.mpeg' ... x-amz-meta-meta: cyberduck1 x-amz-meta-meta: cyberduck2 ... |
Note: Cyberduck uses the last header returned.
| Child pages (Children Display) |
|---|