Project

General

Profile

Actions

Bug #48716

open

aws-s3 incompatibility related metadata

Added by Ilsoo Byun over 3 years ago. Updated over 1 year ago.

Status:
Pending Backport
Priority:
Normal
Assignee:
Target version:
% Done:

0%

Source:
Tags:
backport_processed
Backport:
octopus, pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

When using metadata containing _, the behavior is different from aws-s3.

s3cmd put ~/1m s3://mytest --add-header 'x-amz-meta-key_1: value_1'
s3cmd get --debug s3://mytest/1m

rgw result:

{'headers': {
             ...
             'x-amz-meta-key6-1': 'value_1',
             ...

aws-s3 result:

{'headers': {
             ...
             'x-amz-meta-key6_1': 'value_1',
             ...

The second case is

s3cmd put ~/1m s3://mytest --add-header 'x_amz_meta_key_1: value_1'
s3cmd get --debug s3://mytest/1m

rgw result:

{'headers': {
             ...
             'x-amz-meta-key6-1': 'value_1',
             ...

aws-s3 result:

{'headers': {
             ...


Related issues 3 (1 open2 closed)

Related to rgw - Bug #51772: tempest failures: test_create_container_with_remove_metadata_key/valuePending BackportAli Maredia

Actions
Copied to rgw - Backport #52285: octopus: aws-s3 incompatibility related metadataRejectedActions
Copied to rgw - Backport #52286: pacific: aws-s3 incompatibility related metadataResolvedCory SnyderActions
Actions

Also available in: Atom PDF