When you set the encoding option in your request, you advise the request module to decode the response body using this encoding. This way you ignore the encoding used by the web service, which may or may not be utf-8. You need to find out what encoding the web service was used and use it.
Depending on how satisfied you are with the web service, you can also set the Accept-Charset: utf-8 header.
As your conclusion shows, the web service does not provide the encoding used in the Content-Type header, which is a bad habbit imho.
Sidenote: Content-Encoding is not for encoding, but for compression, gzip migh is a valid value for it.
greelgorke
source share