Should Gemini clients alert users upon redirect?

[Philip Linde]

On Fri, 12 Feb 2021 19:09:30 -0500
Sean Conner <sean at conman.org> wrote:

>   There's a semantic difference between a URL that ends with a '/' and one
> that doesn't.  The one that ends with a '/' is semantically a directory,

According to what spec? "The path component contains data, usually
organized in hierarchical form" (RFC 3986). A URI with a trailing slash
may or may not represent a directory. It may or may not refer to the
same resource as the URI wihout the trailing slash. None of it is
specified. The idea of an URI path as analogous to a filesystem path can
be useful (RFC 3986 uses the file system analogy to describe
dot-segments), but is ultimately just an analogy.

In this case I think it's important to note the difference between a
personal opinion (yours being that there is a semantic difference
between URIs with and without trailing slashes) and specification (RFC
3986's being that there's a syntactic difference but no specified
semantic difference, and only a short note about the semantic meaning
of a path as containing "data, usually organized in hierarchical form").

> and
> to have to add a file per directory to get all URLs to end with a '/' is, in
> my opinion, silly.

Agreed. I've suggested pattern-based path rewrites and rules before,
like Apache or Nginx do. That time I think the question was about how to
best serve multilingual content.

-- 
Philip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://mailing-list-archive.gemi.dev/www/attachments/20210226/e6ca4982/attachment.sig>