I was using Httpcaller for an automation but I could not get it to work. The URL to the service I wanted to use worked fine in the browser but when my automation ran, it resulted in an error from the service saying "invalid URL". It turned out that my URL contained spaces that was encoded as %20 wich the Httpcaller encoded in turn to %2520. Replacing %20 with a space in the Httpcaller solved the problem. Is this desired behaviour?
I'd excpect the Httpcaller to understand not to encode an URL that is already encoded.
