As part of JCLOUDS-217 [1], we've just merged [2] a pull request to
master that removes some long-standing magic in the handling of spaces
during URL encoding [3]. This should, amongst others, help unblock
JCLOUDS-200 [4], which was reverted [5] after causing test failures.
The magic that's being removed was apparently required to deal with
browser and provider quirks in the handling of spaces in URLs. The
expectation is that the number of browsers and providers for which
this may be required has been significantly reduced.
The plan is to monitor for new failures and reintroduce the logic
(ideally using Guava's UriEscapers [6]) where necessary, scoped to the
provider in question. If it turns out that the magic is still required
for many more providers than expected, we would plan to revert this
change.
Please keep an eye out for URL-encoding related weirdness in 1.7.0-SNAPSHOT!
Thanks
ap
[1] https://issues.apache.org/jira/browse/JCLOUDS-217
[2]
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=commit;h=12f29fd8a9e50203acc12ccf794cf73c0abf5703
[3] https://github.com/jclouds/jclouds/pull/82
[4] https://issues.apache.org/jira/browse/JCLOUDS-200
[5]
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=commit;h=bc0abbaa073a9178f3aeb0d1541ea5fc50dded35
[6]
http://docs.guava-libraries.googlecode.com/git-history/242cf19dc4af8779f54038b89d26e56c1b16ed9d/javadoc/com/google/common/net/UriEscapers.html
