keybase / keybase/keybase-issues
Non-descriptive error message on HTTP(S) verification failure
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Error message `could not query example.com. Are you running a site there?` displayed in keybase.io does not give any technical detail why the HTTP request failed.
I suggest complementing it with technical details (e.g. Name Resolution Failure; Unable to connect; Invalid HTTP response etc.).
In my case this message was shown for an on-line website (when using `#1. Host a file on your site` verification method). After some time I was able to verify the website (using the same method).
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or entry point is named in the issue. Locate the HTTP(S) verification failure handling and determine how to distinguish name-resolution, connection, and invalid-response failures; done means the user-facing error includes useful technical detail for the failure while retaining the verification context.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100