Short answer is 'no'. Both UTF-8 and UTF-16 are universal character sets. They can represent any character defined by the Unicode standard.
You should carefully read the error message, and then work out why the UTF-8 scenario is not working. Possible causes are
- the incoming message is claiming to be in some other encoding ( i.e. the source application has set the encoding property incorrectly ).
- the HTTPInput node is explicitly configured to expect UTF-16 data
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum