Martin Conboy (CONBM)
Senior System Architect
Pegasystems Inc.
CONBM Member since 2011 11 posts
Posted: February 8, 2016
Last activity: February 25, 2016
Posted: 8 Feb 2016 13:03 EST
Last activity: 25 Feb 2016 8:04 EST

Can a pega Http Connector rule encode output in UTF-8 ?

I am working for a project in the EU for a customer who wishes to use special characters in an http communication over an http connector. The special characters are the 'Euro' currency symbol, and other accented characters that are not available in 8-bit ASCII.

I believe that internally Pega stores strings as UTF-16 because this is the standard that Java uses. When a Pega http Connector takes a string from a property and sends it to the outside world, it performs some kind of conversion to get an 8-bit representation of the string. I can see that the string I want to send looks correct in the property at the point that the connector is called by using the tracer, however the service at the other end is expecting a UTF-8 encoded string and is throwing an incorrect encoding exception. Somewhere under the hood, Pega is serializing its string for transmission as an 8-bit string. I think it is not performing UTF-8 encoding. I can see no way of specifying the encoding anywhere on the Pega http connector rule.

1. Does anybody know what encoding Pega uses when it serializes a string for output in an http Connector rule?

2. Does anybody know how to specify the encoding for Pega to use, when preparing a transmission in an http Connector rule?

3. Does anybody know a way that I can view, byte for byte, exactly and precisely what got sent? i.e., not just a rendition of it in a browser window, but the exact byte-stream ideally rendered in hexadecimal?


Low-Code App Development System Administration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.