I'm pretty new to node red, and I'm trying to parse an XML file retrieved from HTTP. It's from a lightening detector. I just want to extract a few items and place them in a database, but the XML converter errors out. Flow and XML are pasted in below. When I get the XML and pass it directly to th…

[image] ristomatti: besides your suggestion didn't work out for me worked for me - no regex required - just as i said.... [image] [image] [{"id":"892858e7.6ff808","type":"http request","z":"9b9939a6.d57948","name":"","method":"GET","ret":"bin","paytoqs":false,"url":"http://ccofmobile.thor…

The XML is being returned as UTF16 [image] the http request node isnt able to (OOTB) able to handle that so set the Request node to return a buffer, then pass that through a function and call .toString("utf16le"); e.g. msg.payload = msg.payload.toString('utf16le') return msg;

There seems to also be some garbage characters in the beginning, besides your suggestion didn't work out for me. Instead I used some conversion function found here: https://stackoverflow.com/questions/14592364/utf-16-to-utf-8-conversion-in-javascript .. and after that cleaned the garbage from the b…

Ah, I had the http request node set to its default utf-8 encoding. Nice catch! So @garryadkins , see Steve's example for the cleanest solution unless you already got it working.

It's surprised me how much JavaScript I've learned from this forum even after using it for both work and personal projects for 5-6 years. In the type of work I've done I've never encountered the need for bit operations or character conversion for example.

TBH, the solution should really check the BOM for endianess e.g. a BOM of 0xFE 0xFF indicates big endian (so should call .toString("utf16be") a BOM of 0xFF 0xFE indicates little endian (so should call .toString("utf16le") Now i feel the question is, should the HTTP Request node support a k…

This worked perfect for me. Set the request to binary, change the encoding to utf16 with your line of code and BOOM. Worked perfect. Thanks! -Garry

Well (my thoughts given 2 minute read time) - this is the first time (I can recall) that it has come up in 5 years... (for http node - have seen it for file node), so not keen on adding an option to support it manually, but if autodetect can be seamless and not cause further issues then yes I'd vote…

XML Data returned as UTF16 from HTTP Request doesnt parse in the XML node

General

Steve-Mcl 1 June 2020 07:08 2

Hi, in order to make code more readable and importable it is important to post it between two sets of three backticks - ``` - see this post for more details - How to share code or flow json

Topic		Replies	Views
XML-node XML->JSON Error: Invalid character in name General	20	1989	6 July 2021
GET request of XML page General	12	239	10 November 2023
XML header trips error General http-request , function-node	7	258	23 September 2022
HTTP request GET - JSON parsing error General http-request , function-node	17	614	10 April 2023
(Solved) Getting data from a large dynamic xml General	15	3587	15 July 2019

XML Data returned as UTF16 from HTTP Request doesnt parse in the XML node

Related topics