Project: duracloud
Issue DURACLOUD-440: Handle all unicode characters for storing and retrieving content
This task is to ensure that a content item can be added and retrieved from both DuraStore and DurAdmin using any characters that can be expressed via unicode. Generally, it seems like it's possible to add content items with any unicode content ID, but the problems come in when attempting to access/update/delete those items. These problems are not consistent between DuraStore and DurAdmin. Occationally DuraStore allows for retrieving files that DurAdmin does not. A few Ascii content IDs which currently fail this test are below. This list is not exhaustive, just a examples. test#item - duradmin cannot load content - error when accessing via durastore test%item - duradmin cannot load content - bad request response from durastore test&item - duradmin cannot load content - works fine in durastore test+item - duradmin cannot even bring up metadata - works fine in durastore Of course, content IDs with non-ascii characters also have problems: 1. blankHélènåJör.txt 2. blankπ × { } © 佈 б ' ' —.txt #1 seems to be only a problem in DurAdmin, the file can be retrieved and deleted via DuraStore with no problem. #2 is a problem for both DurAdmin and DuraStore, the file cannot be retrieved or deleted via either.
Story points: 5