[Bug / Feature]: Charset in response headers are not considered while decoding the response text

[balachandarsv]

Is there an existing issue for this?

• [X] I have searched the existing issues

Description

The response contents are always read in UTF-8 charset. Sometimes the response might be in some other charsets which are not considered while decoding the response.

Steps To Reproduce

Try an API which sends the response in UTF-16

Public Sample App

No response

Environment

Production

Issue video log

No response

Version

1.16

[balachandarsv]

Pull request : #20862

[sumitsum]

Hi @balachandarsv can you please confirm if you are still working on this problem ?

[Nikhil-Nandagopal]

Closing this as we haven't seen any updates or issues related to this