comunica / comunica/jQuery-Widget.js
Website does not work with DBpedia fragments after login to Solid authentication
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 20
- Forks
- 43
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
This is because after logging in; we all fetch calls we make are authenticated fetch calls. When really we should only be making authenticated fetch calls to authenticated endpoints.
Instead what fetch needs to do is try unauthenticated fetch, and on 401 figure out what to do (i.e. should it try with authenticated fetch).
We were just encountering this issue on comunica.dev - not sure if this is a new bug since https://github.com/comunica/comunica/pull/1056/files
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 the fetch calls used after Solid authentication in the widget and compare the behavior with the changes in Comunica pull request #1056. Reproduce the DBpedia-fragment failure on comunica.dev; done means unauthenticated endpoints continue working after login while authenticated endpoints still receive authenticated requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, jquery
- Domain
- authentication, frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100