nodeSolidServer / nodeSolidServer/node-solid-server
Malformed uri:s on Windows
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
Windows 10, NSS v5.5.6
Added a Trusted App via the data browser and that resulted in a modified card$.ttl file with malformed URI:s such as:
pim:preferencesFile
<https://rogerfgay.solid.hll.nu:7443%2Fprofile%2Fcard//settings/prefs.ttl>;
Since I'm stuck on Windows, I don't mind trying to fix this, but I'm still a bit of a newbie and would appreciate being pointed to the parts of NSS that are likely to be where the problem is.
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
Start by reproducing the Windows 10 NSS v5.5.6 flow described in the issue: add a Trusted App through the data browser and inspect the resulting card$.ttl file. Trace where the pim:preferencesFile URI is generated, then verify that the saved URI is valid and no longer contains the malformed encoded path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100