AnsweredAssumed Answered

http respond step barf on json body content, bug or known limitation?

Question asked by sdetweil2 on Jul 13, 2015
Latest reply on Jul 14, 2015 by sdetweil2

my simulator service is running well,  except for this one message body to be returned, which kills the HTTP respond step.

I am supplying the body text, thru property replacement in the VSI response selection

 

============================================================================

| Step:        HTTP/S Respond

----------------------------------------------------------------------------

| Message:      : entity reference name can not contain character  ' (position: START_TAG seen ...<bodyAsString>{"******": {        "yyy": "T&P ... @23:64)  :  : entity reference name can not contain character  ' (position: START_TAG seen ...<bodyAsString>{"******": {        "yyy": "T&P ... @23:64)

 

when I put the body thru a JSON validator, I don't find any problems.

 

I have checked for and removed any new lines, tabs,

 

I 'guessing' that @23:64  is trying to tell me something..  row 23 column 64 maybe..

 

----

 

further debug shows that the json body text contains '&',  which for an XML document would need to be encoded..&amp;... but is not a restriction in json..

 

is there a document that describes how an output body in json needs to be formatted so the Respond step can process it correctly?

I don't find this level of detail anywhere.

Outcomes