Does anyone know what the default encoding is for tRESTClient / Talend

[synfield]

I'm getting a Byte Order Mark returned at beginning of XML payload from our external REST service.

It seems to be due to encoding differences between RESTserver and the Talend client.

Can anyone advise what the default encoding set for Talend is, and how I change it?
Thanks.

[Anonymous]

Hi
The default encoding of HTTP payloads will typically be UTF-8. If the target server returns BOM at the start of the UTF-8 encoded sequence and we have a read failure then it is most likely a DOM4J read failure. Looks like we need to open a TESB issue and to investigate how BOM-prefixed sequences can be parsed.
Is the external server configurable somehow so that does not return BOM ?

Thanks, Sergey

[Anonymous]

FYI: https://jira.talendforge.org/browse/TESB-16496

[synfield]

I've got 'log messages' on in advanced setting of tRESTClient.
At the moment, the log output returns

ID: 1
Response-Code: 200
Encoding: ISO-8859-1
Content-Type: application/json; schema=authentication-result

I assume that this means that the response from the REST server is encoded in ISO-8859-1, or is this how Talend is displaying it?

BTW - Thanks, for submitting a bug request for this.

[Anonymous]

I was referring to the other post where a BOM is returned as part of the XML response, and BOM is only available in UTF payloads, right ?
In this particular case do you have a JSON payload with a BOM prefix ? Or XML payload with a BOM prefix ?
Sergey