I’m attempting to post the the rest API from an outside service and have discovered an issue I’m unsure if I can resolve. The service I’m using posts to an API with a content type of “application/x-www-form-urlencoded” instead of plain text.
I’ve confirmed my api post through myopenhab.org works as expected with the plain text content type below:
pi@openhab:~ $ curl --header "Content-Type: text/plain" --request POST --data "ON" https://un:pw@home.myopenhab.org/rest/items/VAR_JoeVoiceCommand
but if I encode with the “application/x-www-form-urlencoded”, the post times out eventually.
pi@openhab:~ $ curl --header "application/x-www-form-urlencoded" --request POST --data "ON" https://un:pw@home.myopenhab.org/rest/items/VAR_JoeVoiceCommand
Is there a configuration file somewhere I could easily update to accept this new content type? Or is this in the design of the API handler?