Gotcha. UTF-8 shouldn't be using a BOM. Sure it's ...
# ktor
m
Gotcha. UTF-8 shouldn't be using a BOM. Sure it's not saving in UTF-16? Anyway, one thing you could try just to get more data would be decoding the bytes into a String using a Reader, then having Jackson decode the string. It's unlikely, but there might be a bug in Jackson's native bytes -> UTF8 decoding?
h
We finally manage this issue using a custom code. In fact, we add a cleanup phase before unmarshalling the response. We have taken out the 3 bytes of the BOM from the response if there exists.
m
Seems reasonable
Unpleasant, but easy to get thorough test coverage of