You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per a recent post on the Gemini mailing list, Matthias Portzel noted that he was preforming a case-sensitive hostname match, and that various other server Gemini implementations don't execute case-sensitive hostname matching, the behaviour of which is clarified in RFC 1034 as per Stephane Bortzmeyer's post.
a-h/gemini is currently doing case-sensitive lookups, and it shouldn't be, as can be tested on my own capsule - gemini://capsule.adrianhesketh.com
The text was updated successfully, but these errors were encountered:
If your users are experiencing this, you'll see a similar error in your server logs:
{"level":"INFO","msg":"gemini: failed TLS handshake","reason":"gemini: certificate not found for \"a-h.GEMINI\"","remote":"127.0.0.1:55359","time":"2021-11-21T14:06:49Z"}
As per a recent post on the Gemini mailing list, Matthias Portzel noted that he was preforming a case-sensitive hostname match, and that various other server Gemini implementations don't execute case-sensitive hostname matching, the behaviour of which is clarified in RFC 1034 as per Stephane Bortzmeyer's post.
a-h/gemini is currently doing case-sensitive lookups, and it shouldn't be, as can be tested on my own capsule - gemini://capsule.adrianhesketh.com
The text was updated successfully, but these errors were encountered: