💾 Archived View for gemini.conman.org › gRFC › 0002 captured on 2020-10-31 at 00:49:42. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
Subject: Resource request format for Gemini
From: Sean Conner <sean@conman.org>
Date: Thu, 1 Aug 2019
Content-Type: text/gemini; format=flowed; charset=US-ASCII;
Status: ACCEPTED
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP 14
[RFC2119] [RFC8174] when, and only when, they appear in all capitals, as
shown here.
HTTP [RFC1945] and Gopher [RFC1436] both suffer from an inability to host
multiple sites on a single server instance because neither protocol required
the full URL [RFC3986] in the request. Gemini should not fall victim to
such a short-shighted requirement. By sending a full URL as the request, a
Gemini server can not only host multiple domains on a single server, but
also allow it to act as a proxy to other Gemini servers.
Therefore, Gemini clients MUST send the entire URL as the request to a
Gemini server when requesting a resource. A Gemini server MAY limit the
length of a URL to 1024 bytes in case of resource contraints on the part of
the server. A client SHOULD NOT send the fragment part of a URL to the
server.
References