cannot use CJK characters in a display name or description of apiproxy

Hi,

I was using CJK characters for display name and description, but after upgrading to 4.51.00, CJK characters are broken and appear as '?'.
I rolled back to 4.50.00 using the VM's snapshot and tested again, but unlike before, CJK characters are broken.
CJK characters are normally displayed in the display name and description of the apiproxy created before the upgrade.

I suspect there is a problem with the OS or browser, so I captured the packet (base64 encoded request payload) sent to edge-ui from the chrome developer tool when saving the apiproxy and tried to decode it, but the CJK string is not broken in the decoded file.

I wonder the management server or cassandra is handling the string incorrectly. How can I get apigee to handle CJK characters properly?

0 1 89
1 REPLY 1

Fortunately, I found the cause, and it was a locale configuration issue.

After setting the LANG environment variable in the VM to ko_KR.UTF-8 , everything works fine.