💾 Archived View for rawtext.club › ~sloum › geminilist › 005308.gmi captured on 2023-09-08 at 17:24:56. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Michael Lazar lazar.michael22 at gmail.com
Wed Feb 17 03:52:47 GMT 2021
- - - - - - - - - - - - - - - - - - -
On Tue, Feb 16, 2021 at 8:53 PM Sean Conner <sean at conman.org> wrote:
Of the two clients I use (generally portal.mozz.us but sometimes the
simple one I wrote), this link causes them to fail:
gemini://idiomdrottning.org/
Namely because both these clients get a redirection to:
gemini://idiomdrottning.org
but both clients will always send:
gmeini://idiomdrottning.org/
(well, I can speak for my own client which does that, I suspect that's
what's happening for portal.mozz.us). There's language in RFC-3986 about
this particular case (section 6.2.3).
-spc
I just pushed an update to the portal.mozz.us proxy to fix this.Actually the code was already in place, but my web framework was doingan automatic redirect on the missing slash to try to be helpful :/ Thefollowing URL should now work without re-adding a trailing slash.
https://portal.mozz.us/gemini/idiomdrottning.org
Your point is well taken though. gemini://example.com andgemini://example.com/ are canonically the same resource and shouldalways return the same response. It took me a while to understand thisbut I now see the light.
- Michael