Hi Chris, Thanks for your response and the insights.
Regarding your questions: - *Core API:* This refers to our internal Java-based API, which we have independently tested by logging the response before it reaches the Ensemble API. The Hindi characters appear correctly at that stage. - *Tomcat Version:* We are using Tomcat version 7.0.41 - *Calls Without Varnish*: We have tested this by calling the API directly through tomcat and through varnish as well. The issue persists in both cases. - Could there be an issue with how Jackson serializes the JSON, causing > certain Hindi characters to break? Unlikely, but possible - Haven't found anything around this. As per what we have found, Jackson by default uses UTF-8 encoding. I'll update you once we gather more findings. Thanks for the insights and suggestions.
