Ugh this is messier than I thought.
The original motivation was to make https://github.com/bouncestorage/swiftproxy
pass swift's functional tests, which tries to put a blob named "dealde%2Fl04
011e%204c8df/flash.png", which won't be escaped by jclouds and causes a number
of failures. I ended up escaping blobs before passing to jclouds, which causes
other problems.
In particular, when we call
putBlob("dealde%252Fl04%20011e%25204c8df/flash.png") jclouds would send the
path as is, which causes the server side to interpret it as "dealde%2Fl04
011e%204c8df/flash.png", and so the latter is what what would be returned from
list(). So now what we put() and what we get from list() are different.
Some o this is captured in https://issues.apache.org/jira/browse/JCLOUDS-918
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/758#issuecomment-107128542
