When adding the Request Header Name Content-Type with the value application/x-www-form-urlencoded, Ventuz seems to append this value to it's own "Content-Type" parameter.
"text/plain; charset=utf-8, application/x-www-form-urlencoded"
When testing the api in a webbrowser it should return:
application/x-www-form-urlencoded without text/plain; charset=utf-8, before.
We want to use the node for a post request.
Thanks in advance!
Please report bugs in this group. We will maybe populate a list of known bugs with a possibly modified description at a later time.
1 post • Page 1 of 1