Why REST Service cannot parse json request if Content-Type header is equal to application/json;charset=UTF-8.
We have a rest service with mapping json request data to Clipboard page. When we sent request with content type = application/json, all works ok. But when content type = application/json;charset=UTF-8, request data is not parsed and Clipboard page is empty as result. In tcp dump request looks ok, for example:
POST /prweb/PRRestService/PegaMKTDataMktEvent/Services/HandleMktEvents HTTP/1.1
Host:host
User-Agent: spray-can/1.3.3
Content-Type: application/json; charset=UTF-8
Content-Length: 139
{"Timestamp":"1494512551378","CustomerID":"EMProfile1WOT_3001130640","EventType":"5cee7434-0302-4dcc-8ef1-3bf9cb094979","EventName":"Test"}
But in logs request data looks like this:
We have a rest service with mapping json request data to Clipboard page. When we sent request with content type = application/json, all works ok. But when content type = application/json;charset=UTF-8, request data is not parsed and Clipboard page is empty as result. In tcp dump request looks ok, for example:
POST /prweb/PRRestService/PegaMKTDataMktEvent/Services/HandleMktEvents HTTP/1.1
Host:host
User-Agent: spray-can/1.3.3
Content-Type: application/json; charset=UTF-8
Content-Length: 139
{"Timestamp":"1494512551378","CustomerID":"EMProfile1WOT_3001130640","EventType":"5cee7434-0302-4dcc-8ef1-3bf9cb094979","EventName":"Test"}
But in logs request data looks like this:
ewogICJDdXN0b21lcklEIjogIkVNUHJvZmlsZTFXT1RfMTIzNDU2NzgiLAogICJUaW1lc3RhbXAi
OiAiMTQ5MzI4MTA2OTk2OCIsCiAgIkV2ZW50TmFtZSI6ICJUZXN0QXJ0aWZhY3QiLAogICJFdmVu
dFR5cGUiOiAic29tZV9hZGRpdGlvbmFsX2luZm9fdG9fYmVfdXNlZF9ieV9jYW1wYWlnbiIsCiAg
IkxhdGl0dWRlIjogNTUuODA2ODcwLAogICJMb25naXR1ZGUiOiAzNy42MjI0MDEKfQ==
How "charset=UTF-8" affects request data?
Accepted Solution
Instellars
IN
Hi,
This was identified as a bug in Pega 7.1.8. If you are on the same version you can request for Hfix-25490. The service rule was updated to handle content type headers with charset.
If you are on lower versions, you can raise a support request from MySupport portal to have this hotfix backported.
This is fixed in Pega 7.2 and above releases.
Accepted Solution
Instellars
IN
Hi,
This was identified as a bug in Pega 7.1.8. If you are on the same version you can request for Hfix-25490. The service rule was updated to handle content type headers with charset.
If you are on lower versions, you can raise a support request from MySupport portal to have this hotfix backported.
This is fixed in Pega 7.2 and above releases.
Pegasystems Inc.
IN
Hello,
Please let us know if you do log an SR for this and its ID. That way we can track it and follow-up this discussion with the resolution.
Thank you,