Page 1 of 1

Simple HTTP Node Request Header Names Conflict

Posted: 11 Apr 2022, 20:32
by cogitator
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!
David