@demobox understand the concern about how close this is to a release but do want to point out that without this change, url encoding is plain broken and some features (like S3 temp signed URLs) can't work without it. Swift seems to work fine because their signatures are not required to be URL encoded (they use base16 whereas AWS uses base64). For instance, try creating `Uris` using `UriBuilder` and pass in something like `http://foo.com/?bar+baz` -- because of the current decode behavior, we'll end up storing the endpoint as `http://foo.com/?bar baz`. Just my 2c.
--- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/82#issuecomment-21979224
