[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Problem with escape characters in when receiving JSon messages trough a rest endpoint

  • Thread starter Thread starter Matt Baker
  • Start date Start date
Status
Not open for further replies.
M

Matt Baker

Guest
Start by verifying the “Content-Type” header on the client request. It MUST state that the character encoding is UTF-8 or UTF-16. JSON requires this. Most webservers are setup to use ISO8859-1 by default as required by the standard. Including PASOE. There was kbase recently created on this. This can be changed, but probably shouldn’t be. So because of this, if the client doesn’t specify character encoding for a message it is assumed to be ISO8859-1. This is wrong for JSON. JSON requires Unicode which is either UTF-8 or UTF-16. This looks like the right single quote from an MS word doc. Unicode Character 'RIGHT SINGLE QUOTATION MARK' (U+2019) Can this character be converted to ISO8859-1?

Continue reading...
 
Status
Not open for further replies.
Back
Top