Don't mangle """username""" and """password""" in "web+" protocol handlers
Open
Nobody has claimed this yet.
security/privacy
topic: custom protocols
- Dominant language
- HTML
- Stars
- 9.4k
- Forks
- 3.2k
- PR merge metrics
- PR metrics pending
Description
Many protocols use at least the """username""" field for semantic, non-credential purposes. This is true with e.g. SSH, which cannot work without it.
And then there's stuff like this: https://soniex2.tumblr.com/post/705832532473724928/so-heres-our-plan-we-wanna-have-web-git-urls
So yeah. The whole mangling stuff just makes URLs less useful for no good reason.
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
Read the issue and its linked example to understand how web+ protocol handlers currently treat username and password fields. Done means the handler behavior no longer mangles fields that protocols use for semantic purposes, including SSH-style usernames.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100