Call should be made successfully with the included accept header
Actual Behaviour
The current included accept header for the Retrieve a schema call is "application/vnd.adobe.xed-id+json"
When making a call with this header, the response is:
{
"type": "http://ns.adobe.com/aep/errors/XDM-1007-400",
"title": "Accept header invalid",
"status": 400,
"report": {
"registryRequestId": "d3c91881-5726-4c3a-aae1-a28ecb1a6b9d",
"timestamp": "06-24-2022 04:12:19",
"detailed-message": "The supplied Accept header is not valid: application/vnd.adobe.xed-id+json - A valid Accept value should look like application/vnd.adobe.'{xed|xdm'}+json; version=1 (Version should be specified)",
"sub-errors": []
},
"detail": "The supplied Accept header is not valid: application/vnd.adobe.xed-id+json - A valid Accept value should look like application/vnd.adobe.'{xed|xdm'}+json; version=1 (Version should be specified)"
}
I was able to get a good response by updating the Accept header to:
application/vnd.adobe.xed+json; version=1
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Download the Schema Registry API collection.
Make a call using "Retrieve a schema" and the included Accept header
Expected Behaviour
Call should be made successfully with the included accept header
Actual Behaviour
The current included accept header for the Retrieve a schema call is "application/vnd.adobe.xed-id+json" When making a call with this header, the response is: { "type": "http://ns.adobe.com/aep/errors/XDM-1007-400", "title": "Accept header invalid", "status": 400, "report": { "registryRequestId": "d3c91881-5726-4c3a-aae1-a28ecb1a6b9d", "timestamp": "06-24-2022 04:12:19", "detailed-message": "The supplied Accept header is not valid: application/vnd.adobe.xed-id+json - A valid Accept value should look like application/vnd.adobe.'{xed|xdm'}+json; version=1 (Version should be specified)", "sub-errors": [] }, "detail": "The supplied Accept header is not valid: application/vnd.adobe.xed-id+json - A valid Accept value should look like application/vnd.adobe.'{xed|xdm'}+json; version=1 (Version should be specified)" }
I was able to get a good response by updating the Accept header to: application/vnd.adobe.xed+json; version=1
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Download the Schema Registry API collection. Make a call using "Retrieve a schema" and the included Accept header
Platform and Version
Sample Code that illustrates the problem
Logs taken while reproducing problem