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

commit c3992339ddb13690347a64f1dab4646fc0c42a16
Author: Solderpunk 
Date:   Thu May 21 15:36:29 2020 +0000

    Make sure response headers have a finite length.

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

--- a/docs/spec-spec.txt
+++ b/docs/spec-spec.txt
@@ -79,23 +79,24 @@ optionally followed by a response body.

 Gemini response headers look like this:

-
+ 

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

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

- is a UTF-8 encoded string of maximum length 1024, whose meaning
-is  dependent.
+ and  are separated by a single space character.

 If  does not belong to the "SUCCESS" range of codes, then the
 server MUST close the connection after sending the header and MUST NOT
 send a response body.

 If a server sends a  which is not a two-digit number or a
- which exceeds 1024, the client SHOULD close the connection and
-disregard the response header, informing the user of an error.
+ which exceeds 1024 bytes in length, the client SHOULD close the
+connection and disregard the response header, informing the user of an
+error.

 1.3.2 Status codes

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