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

commit ec8f417eab0395daad571f8d0b9ec60cae58a3ab
Author: Solderpunk 
Date:   Sun Nov 7 15:15:17 2021 +0100

    Explicitly forbid clients from sending anything after a valid request and require servers to ignore content from naughty clients doing otherwise.

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

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

 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).

+Clients MUST NOT send anything after the first occurence of  in a request, and servers MUST ignore anything sent after the first occurence of a .
+
 # 3 Gemini responses

 Gemini response consist of a single CRLF-terminated header line, optionally followed by a response body.

-----END OF PAGE-----