-- Leo's gemini proxy

-- Connecting to git.thebackupbox.net:1965...

-- Connected

-- Sending request

-- Meta line: 20 text/gemini

repo: gemini-site
action: commit
revision:
path_from:
revision_from: a57e2efb2e5a26f2e2cecc53e93314cb8e6e9d31:
path_to:
revision_to:

commit a57e2efb2e5a26f2e2cecc53e93314cb8e6e9d31
Author: Solderpunk <solderpunk@posteo.net>
Date:   Sun Nov 7 13:18:33 2021 +0100

    Define empty path as equivalent to /, encourage URI normalisation by both servers and clients.

diff --git a/docs/specification.gmi b/docs/specification.gmi

--- a/docs/specification.gmi
+++ b/docs/specification.gmi
@@ -31,7 +31,9 @@ C:   Handles response (see 3.4)

 ## 1.2 Gemini URI scheme

-Resources hosted via Gemini are identified using URIs with the scheme "gemini".  This scheme is syntactically compatible with the generic URI syntax defined in RFC 3986, but does not support all components of the generic syntax.  In particular, the authority component is allowed and required, but its userinfo subcomponent is NOT allowed.  The host subcomponent is required.  The port subcomponent is optional, with a default value of 1965.  The path, query and fragment components are allowed and have no special meanings beyond those defined by the generic syntax.  Spaces in gemini URIs should be encoded as %20, not +.
+Resources hosted via Gemini are identified using URIs with the scheme "gemini".  This scheme is syntactically compatible with the generic URI syntax defined in RFC 3986, but does not support all components of the generic syntax.  In particular, the authority component is allowed and required, but its userinfo subcomponent is NOT allowed.  The host subcomponent is required.  The port subcomponent is optional, with a default value of 1965.  The path, query and fragment components are allowed and have no special meanings beyond those defined by the generic syntax.  An empty path is equivalent to a path consisting only of "/".  Spaces in paths should be encoded as %20, not as +.
+
+Clients SHOULD normalise URIs (as per section 6.2.3 of RFC 3986) before sending requests (see section 2) and servers SHOULD normalise received URIs before processing a request.

 # 2 Gemini requests

-- Response ended

-- Page fetched on Sun Jun 2 17:57:51 2024