-- 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: e7b5c526bd4c147243dacb83be1b25d00f02f9fe:
path_to:
revision_to:

commit e7b5c526bd4c147243dacb83be1b25d00f02f9fe
Author: Solderpunk <solderpunk@posteo.net>
Date:   Sun Nov 29 19:34:34 2020 +0100

    Deprecate implicit gemini scheme of request URLs, making schemes mandatory.  Also remove incorrect use of gemini:// and similar notation.

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

--- a/docs/specification.gmi
+++ b/docs/specification.gmi
@@ -39,9 +39,9 @@ Gemini requests are a single CRLF-terminated line with the following structure:

 <URL><CR><LF>

-<URL> is a UTF-8 encoded absolute URL, of maximum length 1024 bytes.  If the scheme of the URL is not specified, a scheme of gemini:// is implied.
+<URL> is a UTF-8 encoded absolute URL, including a scheme, of maximum length 1024 bytes.

-Sending an absolute URL instead of only a path or selector is effectively equivalent to building in a HTTP "Host" header.  It permits virtual hosting of multiple Gemini domains on the same IP address.  It also allows servers to optionally act as proxies.  Including schemes other than gemini:// in requests allows servers to optionally act as protocol-translating gateways to e.g. fetch gopher resources over Gemini.  Proxying is optional and the vast majority of servers are expected to only respond to requests for resources at their own domain(s).
+Sending an absolute URL instead of only a path or selector is effectively equivalent to building in a HTTP "Host" header.  It permits virtual hosting of multiple Gemini domains on the same IP address.  It also allows servers to optionally act as proxies.  Including schemes other than "gemini" in requests allows servers to optionally act as protocol-translating gateways to e.g. fetch gopher resources over Gemini.  Proxying is optional and the vast majority of servers are expected to only respond to requests for resources at their own domain(s).

 # 3 Gemini responses

@@ -222,7 +222,7 @@ where:

 * <whitespace> is any non-zero number of consecutive spaces or tabs
 * Square brackets indicate that the enclosed content is optional.
-* <URL> is a URL, which may be absolute or relative.  If the URL does not include a scheme, a scheme of gemini:// is implied.
+* <URL> is a URL, which may be absolute or relative.

 All the following examples are valid link lines:

@@ -237,9 +237,9 @@ All the following examples are valid link lines:

 URLs in link lines must have reserved characters and spaces percent-encoded as per RFC 3986.

-Note that link URLs may have schemes other than gemini://.  This means that Gemini documents can simply and elegantly link to documents hosted via other protocols, unlike gophermaps which can only link to non-gopher content via a non-standard adaptation of the `h` item-type.
+Note that link URLs may have schemes other than gemini.  This means that Gemini documents can simply and elegantly link to documents hosted via other protocols, unlike gophermaps which can only link to non-gopher content via a non-standard adaptation of the `h` item-type.

-Clients can present links to users in whatever fashion the client author wishes, however clients MUST NOT automatically make any network connections as part of displaying links whose scheme corresponds to a network protocol (e.g. gemini://, gopher://, https://, ftp://, etc.).
+Clients can present links to users in whatever fashion the client author wishes, however clients MUST NOT automatically make any network connections as part of displaying links whose scheme corresponds to a network protocol (e.g. links beginning with gemini://, gopher://, https://, ftp:// , etc.).

 ### 5.4.3 Preformatting toggle lines

-- Response ended

-- Page fetched on Sun Jun 2 14:21:35 2024