💾 Archived View for bbs.geminispace.org › u › alice-sur-le-nuage › 22883 captured on 2024-12-17 at 15:22:00. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Re: "Server best practices for routing and relative links"
@satch fair enough ! As it happens I'm also implementing my own gemini server at the moment (only out of interest, there's plenty already that would fit my needs), it's interesting to see we're making different design choices (which justifies the fact we need more than one Gemini server so people can choose what they like most).
10 hours ago
@alice-sur-le-nuage, agreed, but every gemini server I've used (on tildes) dumps directories as links. It makes it very simple to get started, and a simple 'touch index.gmi' disables this behavior when required... I believe this is a defacto expected behavior.
I don't think it's a security threat by itself unless you actively insert the links or files you don't want to see into the directory
Server best practices for routing and relative links — I'm writing a gemini server and ran into some gotchas when it comes to relative linking from within gemtext. The server will route gemini requests to paths on the filesystem. i.e. a url "index.gmi" would route to a file named "index.gmi" As a convenience, the server will also resolve requests that correspond to a directory on the filesystem iff the directory contains a file named "index.gmi" Let's say there's a file at the subpath ~subspace/...