Illusory latency due to trailing slash redirects

[colecmac at protonmail.com]

> I also noticed this. Dillo uses whichever URL was loaded first in the
> session (with or without the "/"). It caches the resulting resource,
> with the normalized URL as the cache key. So if you visit
> "gemini://example.horse" first, then subsequently visiting
> "gemini://example.horse/" retrieves the cached response for
> "gemini://example.horse". And you can't remove the cache entry except
> by starting a new Dillo process.


The way I do it in Amfora is normalize each URL for the cache and display,
so that URLs like //example.com:1965/ and gemini://example.com/ aren't cached
twice. And redirects are never cached, although maybe it makes sense to do that
separately.

makeworld