Skip to main content
Solved

HTTP Caller unexpected 400 (bad request)

  • June 6, 2023
  • 2 replies
  • 65 views

albinepro
Supporter
Forum|alt.badge.img+7

I'm using HTTP Caller for geocoding adresses, but somehow I'm getting randomly lot of 400 responses - e.g. 2 of 12 calls are succesfull. If I copy paste the URL from error log to browser I'll get the result correctly.

I'll share the worspace template temporarily including the API key of Geoapify. I don't know why I'm getting 400 (bad request).

Best answer by david_r

You need to manually URL-encode the values when concatenating them with the base URL, especially when using extended characters (accents, etc):

imageAlternatively, the HTTPCaller can do it for you automatically if you use the query string setting rather than manually concatenating the base URL:

imageimage

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

david_r
Celebrity
  • Best Answer
  • June 6, 2023

You need to manually URL-encode the values when concatenating them with the base URL, especially when using extended characters (accents, etc):

imageAlternatively, the HTTPCaller can do it for you automatically if you use the query string setting rather than manually concatenating the base URL:

imageimage


albinepro
Supporter
Forum|alt.badge.img+7
  • Author
  • Supporter
  • June 6, 2023

You need to manually URL-encode the values when concatenating them with the base URL, especially when using extended characters (accents, etc):

imageAlternatively, the HTTPCaller can do it for you automatically if you use the query string setting rather than manually concatenating the base URL:

imageimage

Great, exploding the parameters from URL request to Query String Parameters did the job and is probably more clear for later inspection. Thanks