Chrome complains about scrambled credentials.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go
- Domain
- networking
Research direction
Start by reproducing the report through this HTTPS proxy with Chrome 52.0.2743.116 on Linux amd64, using the example.dev endpoint, and compare the behavior with Firefox. Trace the proxy's credential or TLS handling from its entry point; done means Chrome can process the credentials without the scrambled-credentials error.
Written by the indexing model from the issue text.
Description
On Google Chrome 52.0.2743.116 (Linux, amd64)
You cannot visit example.dev right now
because the website sent scrambled credentials that Google Chrome cannot process.
Firefox works fine.
- Dominant language
- Go
- Stars
- 8
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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.
More from mattrobenolt/https
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
mattrobenolt/https#2 ·
All issues in mattrobenolt/https
Similar issues
-
area/dev-productivity area/disaster-recovery area/ipcei kind/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
kind/bug status/0-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
🤔 refinement needed
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
equinor/radix-operator#1979 ·