Where to make write requests for resources that return 303 for retrieval?
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
e.g. /foo 303's to /bar - some WebIDs do this.
Where should client perform write operations? /foo or /bar?
Should there be a link relation in the header of /bar to /foo (or somewhere else)?
Is this well-documented somewhere e.g. in the depths of https://www.w3.org/wiki/Foaf%2Bssl ?
Examples from the wild would be good to know..
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
Begin with the issue's /foo and /bar 303 example and review the linked FOAF+SSL wiki page. Done means the specification records an agreed write target, any required link relation, and relevant examples.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100