search

opengeospatial / ogcapi-common

OGC API - Common provides those elements shared by most or all of the OGC API standards to ensure consistency across the family.
https://ogcapi.ogc.org/common
Other
45 stars 14 forks source link

Is mimeType for exception correct in schema? #318

Open gfenoy opened 2 years ago

gfenoy commented 2 years ago

I am wondering about the correct Content-Type header to use when returning an exception.

From here, I uderstand that the server should use the following Content-Type header value: application/problem+json, as defined in section 6.1 of the IETF RFC 7807.

On the other hand, from the API-Common-Part-1_1_0.yaml, it seems that the responses 400 and 500 should use: application/json.

Correct me if I am wrong but, I think that the API-Common-Part-1_1_0.yaml should be updated to use application/problem+json as done there, in example: https://github.com/GeoLabs/ogcapi-processes/blob/master/core/openapi/responses/ServerError.yaml.

jerstlouis commented 6 months ago

This is still an issue here:

https://github.com/opengeospatial/ogcapi-common/blob/master/19-072/openapi/3.0/API-Common-Part-1_1_0.yaml#L197

joanma747 commented 6 months ago

This is only a minor change in an example is the schemas.opengis.net that can be requested directly with no need for a corregenda.