I am personally uncomfortable with this patch, due to the huge impact it may have.
Also, I see the *path decode* has ben removed [here](https://github.com/jclouds/jclouds/pull/851/files#diff-22a8e223e58db063094e8c338d8c0b3eL147), but **not** in [this case](https://github.com/timuralp/jclouds/blob/percent-encoding/core/src/main/java/org/jclouds/http/Uris.java#L142). This seems not consistent and likely to produce a broken behaviour. Or I might be wrong, but if this is actually the case, then we definitely do not have a test suite that gives us the confidence I'd like to have to merge this kind of change. Also, the latter `path` is called in several places (when building the URI based on the endpoint, for example). What would happen in that case? What happens to automatically generated endpoints we don't control? Many providers and APIs make use of the `@EndpointParam` and related annotations do dynamically compute the endpoint. How can we have an effective control on the encoding of the URLs in those cases? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/851#issuecomment-137250031
