Workaround for mangled JSON characters

About this task

In some situations, special characters that are submitted in JSON data (UTF-8) from one of the Discover client frameworks can be mangled during processing by Discover. Through the DNCA, you can configure settings to ensure that these characters are properly consumed. If you have enable I18N translation in the Pipeline tab, complete the following steps.

Procedure

  1. In the Pipeline tab of the DNCA Web Console, set the Default request encoding to UTF-8. The request urlfields are defined as being encoded in UTF-8. The DNCA uses UTF-8 encoding if it is not able to detect an encoding type.
    Note: The previous change to flag the request urlfields as encoded in UTF-8 can cause translation issues if the fields are not encoded in ISO 8859 or UTF-8.
  2. Click Save Changes.

Results

Based on the previous configuration changes, the submitted JSON data in UTF-8 is not translated to a different encoding. Since the JSON is submitted in the [RequestBody] section, which is included in the [urlfield] section, setting the default encoding to UTF-8 results in no translation of the data. As a result, it is properly represented inside Discover.