Skip to main content
  • EN

Hi All,

i am using HTTP caller and getting wherein i am passing name text and checking certain parameters but getting an error message as "{"status":"ERROR","messageName":"com.tomtom.cpu.coredb.common.dto.ErrorMessage","messagePayload":{"errorCode":"APPLICATION_ERROR","errorInstanceId":"0da931e0-13b8-444f-aa78-534016b68679","errorDetailedMessage":"Illegal unquoted character ((CTRL-CHAR, code 13)): has to be escaped using backslash to be included in string value
at [Source: org.apache.catalina.connector.CoyoteInputStream@708a538f; line: 1, column: 111]"}}"

Thought this is related to the extra space so i had tried to clean name sting but still it's giving me same error.

Can somebody help me with this ?

Hi @dandekarpriya, the error message seems to indicate that there is a newline (CR: Carriage Return, ASCII code = 13) at the position. If so, try replacing the newline with '\\n', or removing that if unnecessary.

"Illegal unquoted character ((CTRL-CHAR, code 13)): has to be escaped using backslash to be included in string value at ..."

Hi @dandekarpriya, the error message seems to indicate that there is a newline (CR: Carriage Return, ASCII code = 13) at the position. If so, try replacing the newline with '\\n', or removing that if unnecessary.

"Illegal unquoted character ((CTRL-CHAR, code 13)): has to be escaped using backslash to be included in string value at ..."

Thank you takshi . I also suspected the same thing so tried to replace it but then again it gave me the same result.so i am not sure what should i do now to resolve this.

Hi @dandekarpriya, the error message seems to indicate that there is a newline (CR: Carriage Return, ASCII code = 13) at the position. If so, try replacing the newline with '\\n', or removing that if unnecessary.

"Illegal unquoted character ((CTRL-CHAR, code 13)): has to be escaped using backslash to be included in string value at ..."

Has any change in the error message appeared after you replaced a newline? Exactly same as before?

 

 

The error message seems to come from the server, so if possible, have a look in the server logs to see what's going on.

Have you tried using the TextEncoder with URL (percent encoding) on your parameters before transmitting to the server?

Reply


Community Stats

30,032
Posts
114,037
Replies
37,647
Members
Terms & ConditionsCookie settings