CORS proxy support
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
Clients need to use a CORS proxy (for age old reasons.., https://github.com/w3ctag/design-reviews/issues/76 , ..)
Server needs to offer a CORS proxy endpoint.
Doublecheck authn/z requirements..
Related: discover preferred/trusted proxies https://github.com/solid/vocab/issues/26
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
No implementation files or tests are named. Start by reviewing the linked W3C design review and Solid vocabulary issue, then determine the required CORS proxy endpoint and its authentication and authorization requirements. Done means the endpoint behavior and preferred or trusted proxy relationship are specified clearly enough to implement.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100