Problems deleting objects with URL-encoded names in Cloud Files

[smashwilson]

To delete an object with a URL-encoded name from Cloud Files, it looks like you need to double URL-encode the filename:

$ rack files object list --container deconst-drc-content --prefix https%3A%2F%2Fgithub.com%2Frackerlabs%2Fdocs-quickstart%2Fcloud-monitoring
Name                                                                Bytes   ContentType         LastModified
https%3A%2F%2Fgithub.com%2Frackerlabs%2Fdocs-quickstart%2Fcloud-monitoring%2Fgetting-started                    58773   application/octet-stream    2015-06-01T19:00:17.692060
~/ops/deconst-drc-playbook docker:dev (master=)
$ rack files object delete --container deconst-drc-content --name https%3A%2F%2Fgithub.com%2Frackerlabs%2Fdocs-quickstart%2Fcloud-monitoring%2Fgetting-started
error   I couldn't find object [https%3A%2F%2Fgithub.com%2Frackerlabs%2Fdocs-quickstart%2Fcloud-monitoring%2Fgetting-started] in container [deconst-drc-content]
~/ops/deconst-drc-playbook docker:dev (master=) 
$ rack files object delete --container deconst-drc-content --name https%253A%252F%252Fgithub.com%252Frackerlabs%252Fdocs-quickstart%252Fcloud-monitoring%252Fgetting-started
Successfully deleted object [https%253A%252F%252Fgithub.com%252Frackerlabs%252Fdocs-quickstart%252Fcloud-monitoring%252Fgetting-started] from container [deconst-drc-content]

Objects with URL-encoded names also cause rack files container empty to hang.

[jrperritt]

To delete an object with a URL-encoded name from Cloud Files, it looks like you need to double URL-encode the filename

Yes, we ran into this during testing and discussed possible solutions prior to finalizing the implementation, though I can't remember the issues we came up with. I think it had something to do with how Go was auto-encoding the file name vs how another system might auto-encode it (or the users themselves), and then you wouldn't know whether to URL-decode the file name or not. @kenperkins might remember better than I have here. Regardless, that should probably be revisited.

Objects with URL-encoded names also cause rack files container empty to hang.

I'll do some testing. Can you post the output of your empty command with the --log debug flag (minus your credentials, of course)?