URL Proof failing if not in .well-known
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Just tried to verify a domain, placed keybase.txt in the root of the webdir.
Verified that is supplied by the webserver,
Tried to verify with the browser, it fails. Trying a number of times while watching the logs it still fails.
It seems to hit /.well-known/keybase.txt first, get 404 and then hit /keybase.txt
But ignore the 200 on the second attempt
108.162.219.90 - - [13/Jul/2017:04:00:53 -0400] "GET /.well-known/keybase.txt HTTP/1.1" 404 136 "-" "keybase-proofs/2.1.14"
108.162.219.90 - - [13/Jul/2017:04:00:53 -0400] "GET /keybase.txt HTTP/1.1" 200 1675 "-" "keybase-proofs/2.1.14"
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.
Research direction
The report names no source files, tests, or entry points. Reproduce the verification with keybase.txt available at /keybase.txt but not /.well-known/keybase.txt, then trace the URL-proof requests and add coverage so a successful root-path response is accepted as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100