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

Mandatory Response Headers #77

Closed
sachinvodafone opened this issue Oct 17, 2023 · 2 comments
Closed

Mandatory Response Headers #77

sachinvodafone opened this issue Oct 17, 2023 · 2 comments
Labels
documentation Improvements or additions to documentation

Comments

@sachinvodafone
Copy link
Collaborator

I would like to confirm if we have explicitly defined certain response headers as mandatory, which must be present in each API response and that can be validated during our OpenAPI Specification (OAS) spectral validation that we are in the process of defining. I have reviewed the API documentation, but I couldn't find any mention of mandatory response headers.

@sachinvodafone sachinvodafone added the documentation Improvements or additions to documentation label Oct 17, 2023
@eric-murray
Copy link
Collaborator

From the Design Guidelines

To avoid cluttering the CAMARA OAS (Swagger) definition files, the above headers must not be included explicitly in the API definition files even when supported, as it can be assumed that developers will already be familiar with their use.

So it is expected that developers will generally understand which of the standard headers to expect in the response and how to treat them. Several of these are mandatory because of HTTP specifications, not CAMARA specifications. Only "non-standard" headers whose existence somehow affects the use case need be documented, but this will be API dependent, and so will only be reflected in that specific API definition.

Headers "required" by a specific client implementation (for example, if they want to use a standard web browser) are not a concern for CAMARA, but rather for the specific API implementor, who can add the required headers to their own implementation. Providing additional response headers does not make the implementation "non-compliant".

@rartych
Copy link
Collaborator

rartych commented Feb 22, 2024

Closed as agreed

@rartych rartych closed this as completed Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants