keybase / keybase/keybase-issues
Keybase fails to verify web identities that default to HTTP/2.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
One site (https://patrick.burroughs.name/), being served by Apache 2.4. Works with `Protocols http/1.1 h2` in the vhost, fails with `Protocols h2 http/1.1`. Not entirely sure what's up with that — will provide whatever troubleshooting assistance is necessary.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the web-identity verification against the stated Apache 2.4 site using both Protocols orderings, beginning with the working http/1.1 h2 configuration. Compare the failing h2 http/1.1 negotiation and Keybase verification behavior; done means the identity verifies when HTTP/2 is the server's default protocol.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache
- Domain
- authentication, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100