Bug #353
closed
Handle non-ascii filenames
Added by Wido den Hollander over 13 years ago.
Updated over 6 years ago.
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?
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
- Translation missing: en.field_position deleted (
554)
- Translation missing: en.field_position set to 560
- Project changed from 4 to Ceph
- 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
- 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
- Project changed from Ceph to rgw
- Category deleted (
22)
Bulk reassign of radosgw category to RGW project.
Also available in: Atom
PDF