Hello baqwas, which static value string would you recommend. Sorry, but I'm very "green" when it comes to this stuff.
I don't know what context.global.heater1 is supposed to represent in your application. If it is some numerical value then replace this specific string with a number (for now, else ignore my suggestion). Again, not knowing your application and since the goal of the thread is to help you to perform a POST, perhaps the server will accept your POST in the format suggested and then return the XML response that can then be debugged further.
The documentation snippet that you provided illustrated the standard string for ContentType and that string should be present in the msg.header. Also, you may want to retain the User-Agent value in the msg.header too.
Hi bagwas,
Here is what the strings represent in my application:
context.global.heater1 ="0";
context.global.heater2 ="0";
context.global.heater3 ="0";
context.global.heater4 ="0";
context.global.heater5 ="0";
context.global.heater6 ="0";
I replaced the string with a "0", but this did not help the server accept my POST.
My apologies for the delayed response. I've been away from my desk for the past few days.
Does the vendor have a public facing URL for test purposes? Your node is sending the required headers (per vendor's documentation) therefore your success with the browser begs the question on "undocumented" requirement (format or content).
There are many, many tools to debug HTTP requests. I am not partial to any but a Google right now came up with https://www.codepunker.com/tools/http-requests. You may want to try one that you prefer to overcome the current hurdle to craft an acceptable header/payload for your server (that is accepting the browser's submissions).
I'll look for a public site to test your operation too with the following stipulations: GET, query parameters and no authentication key.
Kind regards.
