Verified response from POSTMAN is a valid JSON.
Response from POSTMAN:
{
"displayCatalogMembers": [{
"displayTypeQualifier": "DisplayOfferingGroup",
"id": "123456789",
"name": "Region",
"sequence": 1,
"members": [],
"displayOfferingGroupFilters": []
}]
}
RAW response from Ready API:
{
"displayCatalogMembers": [{
"displayTypeQualifier": "DisplayOfferingGroup",
"id": "123456789",
"name": "Region",
"displayTypeQualifier": "DisplayOfferingGroup",
"sequence": 1,
"members": [],
"displayOfferingGroupFilters": []
}]
}
In RAW response of Ready API we are getting attribute "displayTypeQualifier" twice but not sure why? Why is POSTMAN and Ready API giving different response for the same endpoint and same request. Does the POSTMAN remove the duplicate attributes automatically?
I wish I could provide more insight, but I do not know how to make heads or tails of this. As far as I am aware, both POSTMAN and ReadyAPI (especially in the RAW tab) will show exactly what the service returns, unedited and untouched.
That being said, the only explanation I can think of for this is that, maybe, the service running has a potential issue. I have seen similar behaviors when I have a service running that is clustered between two nodes. One node may be in a bad state, returning bad responses, while the other node works as intended. It's a long shot, but worth looking in to.
Other than that, I'll admit I am stumped.
You are right msiadak, RAW response in POSTMAN is exactly same as the RAW response from READY API, POSTMAN is automatically removing duplicate attributes in the JSON pretty view, but READY API is freaking out with the duplicate attributes. Your insights were helpful in narrowing this done. Thank you for your help.
How can we instruct Ready Api to ignore the duplicate attributes and not freak out? Is it something to do with settings? How can we disable FAIL_ON_READING_DUP_TREE_KEY?
Glad to have been able to help, even just a little. I'll see if I can figure out if there's a setting you can toggle to help. You may want to consider opening a support ticket, too, since this is potentially getting into the nitty gritty details of Ready API. Official support may be of more help.
