REST Response encoding

(imported topic written by JesperLarsen)

Im using the REST API to do some queries against some of the client-data. Some of the data is collected by some analysis, and the other day the queries started to fail. The queries failed because some of the analysis-results were returning the string value of “%1F”. When looking that the queries in the Action Script debugger, the response would be “%1f” but when doing the same request through the REST interface, the %1F is put in as a character, and therefor the XML document is not valid (as it supposedly is conforming to XML v 1.0 as stated in the XML Header). Invalid XML = All kinds of trouble when de-serializing the XML.

To reproduce this, just do a simple:

and the view souce:

<?xml version="1.0" encoding="UTF-8"?>
<BESAPI xmlns:xsi="" xsi:noNamespaceSchemaLocation="BESAPI.xsd">
<Error>This expression contained a character which is not allowed.</Error>

in Chrome will be

This page contains the following errors:

error on line 3 at column 18: invalid character in attribute value

Below is a rendering of the page up to the first error.

… because the %1F (or %03 or whatever special character) is invalid in the XML document

So, how do I set the TEM REST serializer to ignore non-valid XML 1.0- characters, or make it encode these values?


(imported comment written by JesperLarsen)

Got a reply from IBM Support indicating this is an issue.

The issue will be taken care of in a future release 9.X.