Project

General

Profile

Bug #12735

rgw: missing handling of encoding-type=url when listing keys in bucket

Added by Yehuda Sadeh over 7 years ago. Updated almost 7 years ago.

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

0%

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

Description

Opening this bug so that we could track this fix:
https://github.com/ceph/ceph/pull/5579

This is not a full encoding-type handling feature, just solves a specific issue.


Related issues

Copied to rgw - Backport #12856: rgw: missing handling of encoding-type=url when listing keys in bucket Resolved

Associated revisions

Revision 180ca7b5 (diff)
Added by Jeff Weber over 7 years ago

rgw: implement s3 encoding-type for get bucket

This change introduces handling for the encoding-type request
parameter on the get bucket operation. An object key may contain
characters which are not supported in XML. Passing the value "url" for
the encoding-type parameter will cause the key to be urlencoded in the
response.

Fixes: #12735
Signed-off-by: Jeff Weber <>

Revision 609f256a (diff)
Added by Jeff Weber about 7 years ago

rgw: implement s3 encoding-type for get bucket

This change introduces handling for the encoding-type request
parameter on the get bucket operation. An object key may contain
characters which are not supported in XML. Passing the value "url" for
the encoding-type parameter will cause the key to be urlencoded in the
response.

Fixes: #12735
Signed-off-by: Jeff Weber <>
(cherry picked from commit 180ca7b56ba91a3995c76dac698aa4ee31d9a2ce)

History

#1 Updated by Yehuda Sadeh over 7 years ago

  • Status changed from New to Pending Backport

#2 Updated by Loïc Dachary almost 7 years ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF