Merge lp:~fujita-tomonori-deactivatedaccount/swift/s3api-unicode-fix-1 into lp:~hudson-openstack/swift/trunk
Proposed by
FUJITA Tomonori
Status: | Merged |
---|---|
Approved by: | Chuck Thier |
Approved revision: | 176 |
Merged at revision: | 182 |
Proposed branch: | lp:~fujita-tomonori-deactivatedaccount/swift/s3api-unicode-fix-1 |
Merge into: | lp:~hudson-openstack/swift/trunk |
Diff against target: |
22 lines (+2/-3) 1 file modified
swift/common/middleware/swift3.py (+2/-3) |
To merge this branch: | bzr merge lp:~fujita-tomonori-deactivatedaccount/swift/s3api-unicode-fix-1 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Chuck Thier (community) | Approve | ||
Review via email: mp+46687@code.launchpad.net |
Description of the change
Fixes swift3 middleware so that container listings work correctly with utf-8 encoded container names.
To post a comment you must log in.
This still doesn't seem to work completely, but I think the issue is with boto. I imagine boto doesn't try to care about unicode, since I'm pretty sure that you can't have unicode container names. So while the requests work, some of the built in printing functions don't work properly.
To see the errors that I am seeing,
Run the functests, which will leave several containers that have utf-8 encoded container names. If you connect with boto, then run get_all_ containers( ) and print the result, it errors. If you work with the results directly, it seems to work fine. I'm not entirely sure if there is anything that we can do about this. I'll need to think about it a bit more, and discuss with my co-workers.