Project

General

Profile

Feature #5169

Do not list swift containers when enumerating buckets using S3 API

Added by JuanJose Galvez almost 11 years ago. Updated over 4 years ago.

Status:
New
Priority:
High
Assignee:
-
Target version:
-
% Done:

0%

Source:
Support
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

If a user has created containers over swift protocol, they show up in bucket listing over S3, causing problems for anything enumerating buckets over S3 and any S3 clients the customer is using. It would be better to not list buckets that are outside of the S3 specification when listing over S3.

Specifically the issues being seen are in cases where the swift specification allows backslashes and spaces in container names, but attempting to interact with these buckets at all over the S3 api results in a 400 Bad Request error.

History

#1 Updated by Anonymous almost 11 years ago

  • Priority changed from Normal to High

#2 Updated by Anonymous almost 11 years ago

  • Tracker changed from Bug to Feature

#3 Updated by Yehuda Sadeh almost 11 years ago

Can you provide some more logs for this issue, just to make sure that what we think happens actually happens?

#4 Updated by Neil Levine almost 11 years ago

  • Project changed from Ceph to rgw

#5 Updated by Neil Levine almost 11 years ago

  • Status changed from New to 12

#6 Updated by Patrick Donnelly over 4 years ago

  • Status changed from 12 to New

Also available in: Atom PDF