> On 2025 Mar 3, at 04:18, Ramavtar Pareek > <ramavtar.par...@indiamart.com.invalid> wrote: > > 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
Seriously? 7.0.41 is nearly 12 years old, and support for Tomcat 7 ended many years ago. You really, really need to upgrade - there have been hundreds of fixes in Tomcat since then, including critical security-related ones. - Chuck > - *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. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
