keybase / keybase/keybase-issues
How to force web verification over HTTPS?
Open
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I received a notification from Keybase about a failed verification of my website. Nothing changed for a while and I see the Keybade bot coming to grab keybase.txt.
However, it connects via HTTP and my webserver redirects to HTTPS (HTTP code 301). Unfortunately, Keybase does not follow and fails.
Any tip?
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the report about Keybase fetching keybase.txt over HTTP and stopping at the server's 301 redirect to HTTPS. There are no files or tests identified in the issue; a useful outcome would first define the expected verification behavior and where that behavior is implemented.
Written by the indexing model from the issue text.
Assessment
- Domain
- security, web-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100