Problem passing parameters to http_fetch

[WindForce]

Hi
I try to run a GET to some api, using http_fetch, and no matter how i tried to urlencode the parameters, they are always disregarded.

I have the following parameters:

$filter=POR_BOOKNUM eq '2108110096'&$select=IVNUM, DISPRICE

with the spaces in it and the $ signs etc...
When sending from AA with http_fetch the parameters are discarded.
In chrome, calling

https://myurl/myfunction?$filter=POR_BOOKNUM eq '2108110096'&$select=IVNUM, DISPRICE

works perfectly and the parameters are recognized.
Also with postman, works successfully.

Do you have any idea what could be wrong in the way i setup my http_fetch call? tried urlencoding the whole parameters string, as well as urlencode("$filter=POR_BOOKNUM eq '2108110096'")+"&"+urlencode("$select=IVNUM, DISPRICE") but still doesn't work...

Thanks
Jaime

[madtowng]

Hi Jaime,

Is this an API you created, or one you are hoping to consume ?

If the URL works great, it's sometimes easier to use strtran() and stuff() to change the various parts of the URL rather than
mess with the setting for fetch.

[Lenny Forziati]

If you look in the Chrome Developer Tools, you can see how the URL is encoded before being sent to the server when you access the URL with it "unencoded":

encoded.png

[WindForce]

Hi Jaime,

Is this an API you created, or one you are hoping to consume ?

If the URL works great, it's sometimes easier to use strtran() and stuff() to change the various parts of the URL rather than
mess with the setting for fetch.

It's something i'm consuming

[WindForce]

If you look in the Chrome Developer Tools, you can see how the URL is encoded before being sent to the server when you access the URL with it "unencoded":

encoded.png

Thanks Lenny, i think i already tried entering the unencoded string manually, but failed, i may have entered a typo while doint it. Will give it another try...

[madtowng]

Two things.
1. It's always helpful to share the api documentation.
2. You might want to use the url_encode() function if you're not already using it.

[WindForce]

If you look in the Chrome Developer Tools, you can see how the URL is encoded before being sent to the server when you access the URL with it "unencoded":

encoded.png

As i wrote before, i hardcoded the settings.body parameter exactly as shown here, and it still is not recognized correctly, it's as if i didn't set any parameter at all...Will try with curl to check if that will work, but i'm puzzled as to why i can't use http_fetch
Edit: i set the "show before send" flag in the http_fetch call, and i don't see the settings.body at all, just the host name and the headers...i forgot to mention i am trying to run a GET. So i changed to POST and now i see the parameter in the preview, but get some error about content type not set...will keep on digging

[WindForce]

Using Curl this works correctly...weird

[mumfie]

if you test with very simple parameters eg ?p1=123 do the parameters get passed correctly via HTTP get using the query string. Obviously, the API will return an error.

[Lenny Forziati]

As i wrote before, i hardcoded the settings.body parameter exactly as shown here, and it still is not recognized correctly, it's as if i didn't set any parameter at all...Will try with curl to check if that will work, but i'm puzzled as to why i can't use http_fetch
Edit: i set the "show before send" flag in the http_fetch call, and i don't see the settings.body at all, just the host name and the headers...i forgot to mention i am trying to run a GET. So i changed to POST and now i see the parameter in the preview, but get some error about content type not set...will keep on digging

An HTTP get does not use a body, so if you are doing a GET and specifying a POST body, that body will be omitted. This is the correct behavior. You should be sending your parameters as a query string for a GET.

Simply switching to a POST won't work either. While the body will now be sent, you would need to specify the content type of the body, and it sounds this is exactly what the API complained that you did not do. If you are sending what should be a query string as a POST body instead, and it is URL encoded name-value pairs, the correct content type is application/x-www-form-urlencoded

[WindForce]

Thanks Lenny, i realized that after posting my findings here with GET and POST. Putting the whole url in GET still failed for some reason, and i didn't know what content-type to use for POST. Now that you wrote it here, i tested a POST and it finally works as expected...phewww...