[Feature]-[3200]:Setting for different character encodings in API calls

[oskarannas]

Summary

Give the possibility to successfully use APIs that return bodies in other formats than the default UTF-8.

Motivation

An API might for instance return a XML body, encoded in ISO-8859-1 format. Special characters (like the swedish åäö) wont be interpreted correctly and the API response is not useable.

If there were an option for this in the APIs config the user could set the character encoding to be used when interpreting the response.

Additional Context

Example API response with other encoding than UTF-8

HTTP/1.1 200
Transfer-Encoding: chunked
Access-Control-Allow-Origin: *
Content-Type: text/xml; charset=windows-1252
Date: Wed, 13 Jan 2021 13:00:03 GMT

[Nikhil-Nandagopal]

@oskarannas thank you for the feature request! We'll triage how easy / hard it is to add this and try to prioritise this feature

[rohan-arthur]

related #13515

[rohan-arthur]

REST usage, 6m: 4000 apply 10% requirement, 400

Stats

Stat	Values
Reach	400
Effort (months)	0.25

[truongiorocker]

I'm also having this issue where I try to do a POST API call with strings taken from Input fields in Appsmith to my backend. It's a multipart/form-data request.