You’re offline. This is a read only version of the page.
20
Hi,
We have a microservice written in Java Spring boot and we are using RestTemplate with custom interceptor that adds "Accept-Encoding=gzip, deflate, br" in the request headers. This code is working perfectly when we are retrieving entities using Dynamics CRM API 8.x or 9.x. This code has been in production since 2020, but recently last February 27, 2023, approximately this week, we started receiving error when performing the same query using the same code base. The following error is (see below)
JSON parse error: Illegal character ((CTRL-CHAR, code 27)): only regular white space (\r, \n, \t) is allowed between tokens
My assumption is that recently there was an update in Dynamics CRM 365 online in the API that automatically implements compression on the response, and thus this additional interceptor tries to compress the data again. But we would like to inquire if this assumption is correct and what specific update has been implemented by Microsoft on this.
Please advise.
By the way, our quick solution is either remove the interceptor in the code for the RestTemplate, or replace the value "Accept-Encoding=identity"
stackoverflow.com/.../jackson-error-illegal-character-only-regular-white-space-allowed-when-parsi
Share
Report
All responses (
Answers (
