Support Article
Service Rest not handling Request Header with "; charset=UTF-8"
SA-19391
Summary
Unable to map request data elements into clipboard page with Content-Type: application/json; charset=UTF-8 in the header. There were no issues when worked in PRPC 6.3 SP1. It, however, works fine in Pega 7.1.9 when Content-Type: application/json was used instead of Content-Type: application/json; charset=UTF-8 in the header.
Error Messages
Not Applicable
Steps to Reproduce
1. Create a Rest service.
2. Send Content-Type: application/json; charset=UTF-8 in header of request from Chrome Postman/Advanced REST Client.
3. Verify if JSON request is mapped in tracer or clipboard page.
Root Cause
A defect in Pegasystems’ code or rules:
Service Rest not handling Request Header with "; charset=UTF-8"!
Resolution
Apply Hotfix-25920, which supports charset in the Content-Type header.
Published March 14, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.