[spec] Oustanding issues
Stephane Bortzmeyer stephane at sources.org
Mon Jan 11 07:33:32 GMT 2021
On Sun, Jan 10, 2021 at 05:42:34PM +0000,
Martin Keegan <martin at no.ucant.org> wrote
a message of 20 lines which said:
> Clarify whether gemini://host.domain/path and
> gemini://host.domain:1965/path are to be considered equivalent, and
> if so, what that means. (This may be more important for the
> robots.txt side-spec).
Yes, they are equivalent. RFC 3986
<gemini://gemini.bortzmeyer.org/rfc-mirror/rfc3986.txt>, section
3.2.3:
A scheme may define a default port. For example, the "http" scheme
defines a default port of "80", corresponding to its reserved TCP
port number. [...] URI producers and normalizers should omit the
port component and its ":" delimiter if port is empty or if its
value would be the same as that of the scheme's default.
For instance, the Lupa crawler
<gemini://gemini.bortzmeyer.org/software/lupa/> canonicalizes
<gemini://host.example:1965/path> to <gemini://host.example/path>.
% lupa-insert-url gemini://host.example:1965/path
URL gemini://host.example:1965/path added to the database (ID 152155, capsule ID 571)
% my-lupa-insert-url gemini://host.example/path
URL gemini://host.example/path already in the database
Archive home | About this archive