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.

Sign up for GitHub

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

Jump to bottom

Response headers #123

Open
csarven opened this issue Nov 24, 2019 · 0 comments
Open

Response headers #123

csarven opened this issue Nov 24, 2019 · 0 comments
Labels
doc: Protocol topic: resource access

Comments

@csarven
Copy link
Member

csarven commented Nov 24, 2019

Basically looking for potential patterns here that can be used to make implementations simpler or efficient.

  • Are there headers that should be present in all responses or alternatively for a set of methods eg. Specify PATCH #85 (comment) proposes Accept-Patch to be in all responses (regardless of issued request method) for resources that can be PATCHable.
  • If at all, how would the headers in OPTIONS response be different than the rest of the methods?
  • ..
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
doc: Protocol topic: resource access
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kjetilk @csarven