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

commit efd5cab005a0d11b5641ee5351d1905ce8e53814
Author: Solderpunk <solderpunk@sdf.org>
Date:   Wed Oct 23 16:18:35 2019 +0000

    Clarify whitespace in response headers.

diff --git a/spec-spec.txt b/spec-spec.txt

--- a/spec-spec.txt
+++ b/spec-spec.txt
@@ -1,7 +1,7 @@
 -----------------------------
 Project Gemini
 "Speculative specification"
-v0.9.1, August 11th 2019
+v0.9.2, October 6th 2019
 -----------------------------

 This is an increasingly less rough sketch of an actual spec for
@@ -79,11 +79,13 @@ optionally followed by a response body.

 Gemini response headers look like this:

-<STATUS> <META><CR><LF>
+<STATUS><whitespace><META><CR><LF>

 <STATUS> is a two-digit numeric status code, as described below in
 1.3.2 and in Appendix 1.

+<whitespace> is any non-zero number of consecutive spaces or tabs.
+
 <META> is a UTF-8 encoded string of maximum length 1024, whose meaning
 is <STATUS> dependent.

-- Response ended

-- Page fetched on Sun Jun 2 14:32:19 2024