Relative links sometimes fail to resolve.

[humberto-ortiz]

I have an unusual problem with some relative links in lagrange 1.19.4 on linux (aarch64, Debian 13)

In a directory called a, if I have an index.gmi that links to b.gmi lagrange sometimes fails to resolve the relative link as a/b.gmi

If I browse to gemini://example.com/a without a trailing slash, I get the correct index, but the link to b.gmi will resolve to /b.gmi, not a/b.gmi. Other gemini clients do resolve the uri correctly, so I don't think its a server issue. If I browse gemini://example.com/a/ with the trailing slash it works.

Here's an example: gemini://azul.archipielago.uno/a vs gemini://azul.archipielago.uno/a/

[skyjake]

I don't see any incorrect behavior here. The relative URI resolution rules are so that if you're viewing the page "/a", a relative link to "b.gmi" is assumed to be relative to the same directory where "a" is located, i.e., "/". Thus it resolves to "/b.gmi". When the slash is present at the end, that means you're actually viewing the index page of the directory (whatever the server determines that to be). In that case, the directory for resolving relative paths is "/a/", and it will resolve to "/a/b.gmi".