Bug #48716
open
aws-s3 incompatibility related metadata
Added by Ilsoo Byun over 3 years ago.
Updated over 1 year ago.
Backport:
octopus, pacific
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': {
...
- Pull request ID set to 38737
- Status changed from New to Resolved
- Assignee set to Ilsoo Byun
- Target version set to v17.0.0
This looks to me like something that should be backported to nautilus (near end-of-life), octopus, and pacific. Any objection?
- Status changed from Resolved to Pending Backport
- Backport set to octopus, pacific
This looks like a bug fix that needs backports.
Also, rather than re-implementing the same algorithm 3 separate times, I think a function that could be called from all these places would have removed some technical debt.
- Copied to Backport #52285: octopus: aws-s3 incompatibility related metadata added
- Copied to Backport #52286: pacific: aws-s3 incompatibility related metadata added
- Related to Bug #51772: tempest failures: test_create_container_with_remove_metadata_key/value added
- Tags set to backport_processed
Also available in: Atom
PDF