web proof fails for http: has already succeeded for https:

I am [https://keybase.io/kerrybenton](https://keybase.io/kerrybenton)

I have verified my web identity over https via text file [here](https://www.kerrybenton.com/keybase.txt)

The same file is available via http. I note that the file indicates https as the protocol, but the instructions on keybase.io don't address this, and I can't seem to create a new signature file for http only.

Is it just a matter of editing the file to add that protocol? Should the signature file generator not give the option to handle http and https at the same time, and leave the success / failure of each to whether the https:// request succeeds?

None of this is obvious, in spite of the otherwise very easy-to-manage processes and generators built by the keybase team.

Start by reviewing the issue's keybase.txt example and reproducing web identity verification over both HTTPS and HTTP. Determine whether the failure is in proof-file generation, protocol handling, or the verification instructions; done should be a decided and documented behavior for identities available through both protocols.

Written by the indexing model from the issue text.