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

commit 5f8700ba976abfea8e4fbfc6162d7ca8d518858a
Author: Solderpunk 
Date:   Thu Jul 2 17:25:14 2020 +0000

    Disambiguate  in response header.

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

--- a/docs/specification.gmi
+++ b/docs/specification.gmi
@@ -2,7 +2,7 @@

 ## Speculative specification

-v0.14.1, June 15th 2020
+v0.14.2, July 2nd 2020

 This is an increasingly less rough sketch of an actual spec for Project Gemini.  Although not finalised yet, further changes to the specification are likely to be relatively small.  You can write code to this pseudo-specification and be confident that it probably won't become totally non-functional due to massive changes next week, but you are still urged to keep an eye on ongoing development of the protocol and make changes as required.

@@ -55,6 +55,8 @@ Gemini response headers look like this:

  is a two-digit numeric status code, as described below in 3.2 and in Appendix 1.

+ is a single space character, i.e. the byte 0x20.
+
  is a UTF-8 encoded string of maximum length 1024 bytes, whose meaning is  dependent.

  and  are separated by a single space character.

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