Do not use a weak ETag in `If-Match`
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 3
- Avg merge
- 11h 46m
- Merged PRs (30d)
- 3
Description
Currently, source-pane will put any found ETag into the If-Match header of its requests.
However, as discussed in https://github.com/solid/specification/issues/340#issuecomment-954892300, servers MUST perform a strong comparison. Hence, when sending any weak ETag, comparison will always fail.
The source pane should thus not use a weak ETag, and perhaps use another semaphore mechanism.
Contributor guide
No contributing guide indexed for this repository
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 tracing how source-pane obtains ETags and builds the If-Match header, using the linked Solid specification discussion as context. The work is done when weak ETags are no longer sent in If-Match and the resulting request behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100