Invalid JSON body for status code 404
Jim Larson
1
Reputation point
Scenario:
DI4 2024-11-30 and DI3.1 2023-07-31.
Result id that doesn't exist is used with analyzeResults endpoint. Status code 404, NotFound is returned. Expect JSON response body conforming to ErrorResponse per
Actual response body is:
{"code":"NotFound","message":"Analyze result does not exist."}
Response is Error instead of ErrorResponse. I have tests and other code that suggest ErrorResponse was returned at some point in the past. I believe this is an undocumented behavior change or a bug.
Sign in to answer