Trusted Applications: Disallow invalid Origin values / strip trailing slashes
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 106
- Forks
- 52
- Avg merge
- 13h 35m
- Merged PRs (30d)
- 10
Description
It is a common and frustrating mistake to put a slash at the end of the Origin value (see e.g. https://gitter.im/solid/chat?at=5f201ed23eef7e1ffe3c40b4)
The UI should validate if the value is a valid Origin value, aka Origin: <scheme> "://" <hostname> [ ":" <port> ] (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Origin)
Especially it should disallow or auto-remove trailing slashes
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
No file or test is named; start by locating the trusted-application UI and its Origin value handling. Compare the accepted value with the linked Origin format, and consider the trailing-slash behavior described in the issue. Done means invalid Origin values are rejected or trailing slashes are removed consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100