> can we get JCLOUDS-200 working without this change by encoding the URL first, > or is it broken even then?
@demobox we can't -- it is broken because as soon as you hand a HTTP request that contains a '+' in the query string to jclouds `BaseHttpExecutorService`, it will mange the request and wrongly convert the '+' to a space before issuing the request. JCLOUDS-200 just fixes a similar problem on the request being _generated_ by jclouds. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/82#issuecomment-21988773
