Skip to main content
  • EN

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.

If I remember correctly the HTTPCaller did no url encoding in earlier versions which caused issues for users. This was fixed later so I believe this is expected behaviour.

 

Edit: We checked with an encoded url and it just works fine, using desktop 2019.1.2. Does it work for you in desktop but not in server? What fme version?

Reply


Community Stats

29,705
Posts
112,905
Replies
37,360
Members
Terms & ConditionsCookie settings