Project

General

Profile

Actions
Copy link

Bug #353

closed

Handle non-ascii filenames

Added by Wido den Hollander over 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

Yesterday i made a script which uploaded some random files to my S3 gateway just to test it.

In this batch there was a file with the name: Nova.ScienceNOW.0403.Marathon.Mouse.Dinosaur.Plague.Franklin.Chang-D??az.Space.Storms.mkv

When listing the bucket contents i got a XML malformed error from my browser since this was not placed between CDATA tags.

Should we limit key names to ASCII only or accept other characters then ASCII?

Actions
Copy link
 #1

Updated by Wido den Hollander over 13 years ago

I just checked the Amazon docs about this: http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1109#07

Right now there is no check on a bucket or object name, if it is UTF-8 or below 1024 characters.

I think we should do so. But then in a bucketlisting the names should be placed between CDATA, otherwise the XML parser will fail.

Actions
Copy link
 #2

Updated by Colin McCabe over 13 years ago

Yeah, I agree with Amazon's approach here. UTF-8 makes sense. I think we could continue to use std::string internally with this approach.

As an aside, apparently displaying filenames with control characters in some versions of "eterm" and other popular terminal emulators can be a security breach:

http://seclists.org/fulldisclosure/2003/Feb/att-341/Termulation.txt

Actions
Copy link
 #3

Updated by Sage Weil about 13 years ago

  • Translation missing: en.field_position deleted (554)
  • Translation missing: en.field_position set to 560
Actions
Copy link
 #4

Updated by Sage Weil about 13 years ago

  • Project changed from 4 to Ceph
Actions
Copy link
 #5

Updated by Sage Weil about 13 years ago

  • Category set to 22
Actions
Copy link
 #6

Updated by Sage Weil about 13 years ago

  • Status changed from New to Resolved
  • Translation missing: en.field_story_points changed from 0 to 1
  • Translation missing: en.field_position deleted (582)
  • Translation missing: en.field_position set to 582
Actions
Copy link
 #7

Updated by Sage Weil about 13 years ago

  • Translation missing: en.field_story_points changed from 1 to 3
  • Translation missing: en.field_position deleted (582)
  • Translation missing: en.field_position set to 582
Actions
Copy link
 #8

Updated by John Spray over 6 years ago

  • Project changed from Ceph to rgw
  • Category deleted (22)

Bulk reassign of radosgw category to RGW project.

Actions
Copy link

Also available in: Atom PDF