💾 Archived View for rawtext.club › ~sloum › geminilist › 001492.gmi captured on 2020-10-31 at 02:19:13. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
Felix Queißner felix at masterq32.de
Wed Jun 10 12:15:33 BST 2020
- - - - - - - - - - - - - - - - - - -
How is gemini meant to deal with authority's userinfo?
gemini://username:password@mozz.us/
gemini://username@mozz.us/
Orthodox?
If so, how does the server communicate authentication failure back to the client? I don't think that user/password is the right way to handleauthentication in Gemini. The URL RFC also specifies:
Use of the format "user:password" in the userinfo field is
deprecated.
So only user@… is still a valid URL.
If your server handles user@ in a different way than without authority,i think that's totally in-spec, but authentication is probably not.
One possible usage for authority could be home-dirs instead of anofficial site:
Instead of using=
gemini://random-projects.net/~felix/one could also access the directory via=
gemini://felix@random-projects.net/
But that's just some brainfart.
Regards- xq
[0] https://tools.ietf.org/html/rfc3986