Illusory latency due to trailing slash redirects

[Philip Linde]

>   Semantically (and stated in RFC-3986) they are separate resources.  For a
> fun time, try the following two links:
> 
> 	gemini://gemini.conman.org/test/doc1
> 	gemini://gemini.conman.org/test/doc1/

Those two are, but consider these:

	gemini://gemini.conman.org
	gemini://gemini.conman.org/

Per RFC 3986, they should be equivalent. A server respecting the
standard should understand an authority without a path specified as
referring to the path "/". This is described in section 6.2.3.

Of course, this is "in general" for schemes using authorities¸ and I
guess a scheme can define its own normalization rules, but AFAIK no
exceptions to this have been specified for Gemini.

On that basis I think servers that serve different content on these
should fix it to mean exactly the same thing.

For URLs that have paths specified like in your example, clients should
as you say be able to handle them being different because there are no
such normalization rules for URLS with paths specified.

Best regards,
Philip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20200628/56c5d513/attachment.sig>