I have contacted the application where I'm connecting to, but their logs say they haven't received any requests, and so it must be on our server side. I can connect to the API with Postman, just not with Wappler somehow.
Yes it seems that the most recent version of wappler automatically retrieves the data of the headers section to the fetch window, so I didn’t change anything there. I didn’t manually fill in that field in fetch.
And so when the fetch works fine, it’s strange that the actual live version doesn’t work. This is btw the only api that has this, I’ve tried several other api’s and they all work fine.
You can test with https://requestinspector.com. Just generate an hook there and change the url of your API action, then you can see what the actual data is that is send to the endpoint.
Yes I know this, but that isn’t solving the problem.
This is all correct.
Again, it works fine when I use postman, just not in Wappler. I’m pretty sure I’ve done everything like I’m supposed to. Is there anything you can check on your side?
I just did test this from another server, got the same problem. But then I contacted the developer of this API, they told me they received the header name in lower case, while they required it to be with the first letter as a capital letter. They corrected this on their side, and then I could connect again.
So my question is, does Wappler convert all header names/values to lower case?
Good that you figured out what was wrong and that they could solve that in the API. The headers are normally not case sensitive, Wappler doesn’t convert them to lowercase, the problem is the HTML DOM. We use standard HTML DOM in App Connect, so components are just tags and attributes, problem is that the DOM is not case sensitive, and it returns all attribute names in lowercase. That is why it was converted, we will have a look on how to improve this.
should I send an error report?