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

document a *should* for the location header #255

Open
toumorokoshi opened this issue Dec 30, 2024 · 0 comments
Open

document a *should* for the location header #255

toumorokoshi opened this issue Dec 30, 2024 · 0 comments

Comments

@toumorokoshi
Copy link
Member

From aep-dev/aep-openapi-linter#11, @mkistler has called out that we should include a location header in the HTTP request, to adhere to RFC 9110:

Other possible rules:

There must be a 201 response (possibly covered by aep-133-response-schema)
The 201 response has a location response header (RFC 9110 Section 15.3.2)

We should add that. Also a follow-up question: should we be doing more to hotlinking to the RFCs we've adopted and attempt to adhere to in the spec?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant