Hi, Gordhan,
 Can you provide a minimum reproducible example? Need to include HTTP
header information, such as Content-Type and Accept-Charset

Thanks,
Ming Wen, Apache APISIX PMC Chair


On Tue, 1 Apr 2025 at 15:39, Gordhan Lal Goyal <gordhan.go...@pinelabs.com>
wrote:

> Hi @Ming Wen <wenm...@apache.org>,
> I am writing to bring your attention to an issue we are currently facing
> with our API gateway implementation using *Apache APISIX(v3.2.2)*. We
> have identified a problem related to the transmission of vernacular
> languages (regional languages in India) through our system.
>
> *Problem Statement:*
> When we are passing vernacular language content in a field to the upstream
> service via APISIX, we have observed that the original message is not being
> transmitted accurately. Instead, the upstream receives garbled text,
> compromising the integrity of the data. [Facing issue with languages like
> Hindi, Telugu, Tamil, Kannada, Marathi, Malayalam, Gujrati etc etc in short
> except English, we are facing this issue with all other regional languages
> in India]
>
> *Example**: *
> This is the request we are passing.
> This is what is received by the upstream:
>
>
> * Objective:*
>
> Our primary goal is to ensure that the exact message in vernacular
> languages is successfully transmitted via APISIX to the upstream service,
> preserving its original form and meaning.
>
> *Request For Support:*
>
> We are seeking solutions to resolve this data transmission issue.
> Specifically, we need to implement measures that will allow APISIX to
> handle and forward vernacular language content without corruption or loss
> of information.
> Or can you please help us with your inputs on the same.
>
> Thank you for your prompt attention to this matter. We look forward to
> your response and assistance in resolving this issue.
>
>
>
> Thanks & Regards
>
> *Gordhan Lal Goyal*
> CONFIDENTIALITY NOTICE This e-mail message and any attachments are only
> for the use of the intended recipient and may contain information that is
> privileged and confidential. If you are not the intended recipient, you are
> hereby notified that any disclosure, distribution or other use of this
> e-mail message or attachments is strictly prohibited. If you have received
> this e-mail message in error, please permanently delete the email and its
> attachments and notify the sender immediately. Thank you.
>

Reply via email to