AnsweredAssumed Answered

HTTP Client step outputs with the bad encoding (LATIN1 / UTF-8)

Question asked by B932F9CY on Jun 5, 2018

I'm unsure if this is a bug or a bad configuration from my part. I'm using HTTP Client in one transformation and the resulting XML always come with a bad encoding, transforming special characters like é to é.

The step is configured to expect UTF-8 data. If I open the URL directly in my browser, it renders the characters as expected using UTF-8. The XML header also states the encoding of the file as UTF-8. I've tried with multiple XML files from multiple domains, all are behaving like that. Am I missing some kind of configuration from my part? I have no idea on why this step is returning these broken characters.

I'm using Pentaho Data Integration on Linux, Debian-based.