Parameter not read

[koswarabilly]

from my last issue which is content-type have been fixed #89 ,but come new problem which is parameter
i want to put some parameter when i try to get respond from certain url

when i try to execute this come out as error

is it the right format to pass in parameter?
because me and my colleague discover that fusio pass the right header content-type but it do not pass the right parameter
or am i getting the wrong assumption?

[zaniar]

Could you try to make a request to http://192.168.51.45:8787/erp-ws-main/ws/postdata using curl, postman, insomnia, or something else?

I think this is not Fusio's issue. More likely an issue with your target server.
Do you really following the manual about how to connect to your target server correctly?

[koswarabilly]

I tried it with postman and i get a result
The url and parameter are copied from postman
As i say if the url from the SS and the parameters from the SS are linked with '?' It is the url i copied from postman

[chriskapp]

Mhh ok I think the problem is that you want to send your data encoded as application/x-www-form-urlencoded. The HTTP action currently only sends data as application/json to the endpoint. That being said you can send application/x-www-form-urlencoded content to Fusio but the HTTP action will then send the request as application/json to your endpoint. If you remove the Content-Type header and simply enter {"foo": "bar"} as body, what is the response of the server?

[koswarabilly]

i tried postman and insomnia and both successfully return a result here are the screenshots
@zaniar

@k42b3
do you mean it like this?i don't change the url,parameters, & method

if i keep the content-type=application/x-www-form-urlencoded, it give me the same error as earlier post screenshots

[chriskapp]

Ok, yes then this is the problem, that we always send the body JSON encoded. I have started to improve the HTTP Adapter so that you have beside the URL field another select box Content-Type where you can select the content type of the request payload. The adapter uses the the options json or form_params key in the guzzle request. I will let you know if this is implemented. Then you need to add the responseCode, responseParam and authParam Field to the body.

[koswarabilly]

thankyou @k42b3

[chriskapp]

So I have update the HTTP adapter. If you dont want to wait for the next release you could also update the adapter through composer, i.e. simply using the following command:

composer update fusio/adapter-http

[chriskapp]

The latest release includes now also the updated http adapter