Support Article
Service Rest not handling Request Header with "; charset=UTF-8"
SA-18248
Summary
User is upgrading from 6.3 SP1 to Pega 7.1.8. There are standard APIs in customer implementation that generate REST API headers with "Content-Type: application/json; charset=UTF-8".
User's Service-REST clients are invoking the service by passing "Content-Type: application/json; charset=UTF-8" in the header of request. Application in 6.3 SP1 provides a Service-REST and is working fine in the LIVE system. When clients are invoking same in Pega 7.1.8 with same "Content-Type: application/json; charset=UTF-8" in the header, Pega 7.1.8 application is unable to map request data elements into clipboard page.
Pega 7.1.8 application failed to map request data elements to clipboard page which was working fine into Pega 6.3 SP1. It works fine in Pega 7.1.8 when they send "Content-Type: application/json" in the header instead of "Content-Type: application/json; charset=UTF-8". But clients have major impact if they have to change Content Type to application/json.
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 in tracer or in clipboard page that whether JSON request is mapped.
Root Cause
A defect in Pegasystems’ code or rules.
Resolution
Apply HFix-25490.
Published January 31, 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.