Response headers
Open
Nobody has claimed this yet.
doc: Protocol
topic: resource access
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
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. https://github.com/solid/specification/issues/85#issuecomment-555466311 proposes
Accept-Patchto be in all responses (regardless of issued request method) for resources that can be PATCHable. - If at all, how would the headers in
OPTIONSresponse be different than the rest of the methods? - ..
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked specification issue 85 discussion and compare the proposed Accept-Patch behavior with the questions about all responses and OPTIONS responses here. Done means reaching and documenting a clear consensus on which headers apply to which resources, methods, and response types.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100