Response XML formatting tab doesn't work when response charset is not UTF-8

Description

When inspecting XML responses encoded in ISO-8859-1 charset (and probably any encoding other than UTF-8) , the XML formatting tab displays "Invalid XML Data" instead of the actual XML Data.

This happens even tough the content-type header properly specifies the response charset:

Content-Type: text/xml;charset=ISO-8859-1

Possible root cause

The charset parameter in the content-type HTTP response header is probably ignored and the response is wrongly interpreted as UTF-8.

Proxyman version

Version 2.32.1 (23210)

macOS Version

mac 11.5.2

Steps to reproduce

The attached test-charset.tar.gz archive contains one UTF-8-encoded XML file and one ISO-8859-1-encoded xml file.

It also contains a simple node project that uses the serve npm module that creates a local http server serving the two files with their correct charset set in the content-type header.

• Install node.js on your local computer.
• Download the following node project: test-charset.tar.gz
• Untar the archive:

tar xfz ./test-charset.tar.gz

• Install node dependencies (the serve npm module, actually)

npm install

• Launch the local web server

npx serve

• Launch proxyman
• In another terminal, run the following two commands:

curl --proxy "http://localhost:9090"  http://0.0.0.0:5000/response.xml
curl --proxy "http://localhost:9090"  http://0.0.0.0:5000/response.ISO-8859-1.xml

• Kill the server command
• Open the corresponding responses in proxyman

Observed behavior

• The xml response tab correctly formats for the response.xml request ✅
• The xml response tab displays "Invalid XML Data" for the response.ISO-8859-1.xml instead of the actual data 🚫

Expected behavior

Both XML responses should be formatted correcly