Closed sfnuser closed 1 year ago
I've no issue with using application/problem+json
for errors rather than application/json
, but the client will find RFC 7807 no help at all for interpreting the fields that are currently returned.
Do you also plan to propose changes to the CAMARA design guidelines to make error responses RFC 7807 compliant? If not, then this could be misleading for the client, who might have a common way of processing any errors labelled application/problem+json
.
I agree. Also, none of the CAMARA APIs seems to return RFC 7807 compliant error response. Modifying QoD API alone to change ErrorInfo
to problem details format may not make sense at this point unless it is driven from the Commonalities group.
Discussed, can be closed. Further discussion within Commanalities.
While create a PR for #83, I noted that all the error responses in the spec that carry
ErrorInfo
schema in the body should have the content type set toapplication/problem+json
instead ofapplication/json
.I decided to create this as a separate issue so that a PR release can be planned accordingly.