Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is mimeType for exception correct in schema? #318

Open
gfenoy opened this issue Sep 15, 2022 · 2 comments
Open

Is mimeType for exception correct in schema? #318

gfenoy opened this issue Sep 15, 2022 · 2 comments
Labels
Part 1 Applicable to Part 1 Core

Comments

@gfenoy
Copy link

gfenoy commented Sep 15, 2022

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
Copy link
Member

@joanma747
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Part 1 Applicable to Part 1 Core
Projects
Development

No branches or pull requests

3 participants