I've been thinking of where the reliance on *not* encoding the string -- the crux of this change -- could have been successful. No obvious examples come to mind that would still function. For example, putting a key "%24" would actually put "$" -- the user would notice this when listing the bucket.
I think the biggest issue is that user's may need to update their code to *not* work around this issue. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/851#issuecomment-138672187
