Project

General

Profile

Actions

Bug #1287

closed

Setting metadata with unreadable characters is not consistent with amazon S3

Added by Stephon Striplin almost 13 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

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

Description

If you have a string like '\x04world', Amazon will encode it using MIME encoded-word syntax. Currently, our S3 implementation will either give a 403 error if the string begins or ends with an unreadable character, or it will store it as raw input, rather than use Amazon's method.

Actions

Also available in: Atom PDF