repo: gemini-site
action: commit
revision: 
path_from: 
revision_from: c11cd4fa708b763548a687b6081351811bf3f83f:
path_to: 
revision_to: 
git.thebackupbox.net
gemini-site
git clone git://git.thebackupbox.net/gemini-site
commit c11cd4fa708b763548a687b6081351811bf3f83f
Author: Solderpunk 
Date:   Mon Jun 15 15:46:55 2020 +0000

    Fix section numbering error.

diff --git a/docs/specification.gmi b/docs/specification.gmi
index 33d7c6b111f7f2bafda6008fca18e6d03d63bb68..
index ..4d5316fcb8d6e83773dea81a899b2424f31bd9b4 100644
--- a/docs/specification.gmi
+++ b/docs/specification.gmi
@@ -81,31 +81,31 @@ Status codes beginning with 2 are SUCCESS status codes, meaning:

 The request was handled successfully and a response body will follow the response header.  The  line is a MIME media type which applies to the response body.

-### 3.3.3 3x (REDIRECT)
+### 3.2.3 3x (REDIRECT)

 Status codes beginning with 3 are REDIRECT status codes, meaning:

 The server is redirecting the client to a new location for the requested resource.  There is no response body.   is a new URL for the requested resource.  The URL may be absolute or relative.  The redirect should be considered temporary, i.e. clients should continue to request the resource at the original address and should not performance convenience actions like automatically updating bookmarks.  There is no response body.

-### 3.3.4 4x (TEMPORARY FAILURE)
+### 3.2.4 4x (TEMPORARY FAILURE)

 Status codes beginning with 4 are TEMPORARY FAILURE status codes, meaning:

 The request has failed.  There is no response body.  The nature of the failure is temporary, i.e. an identical request MAY succeed in the future.  The contents of  may provide additional information on the failure, and should be displayed to human users.

-### 3.3.5 5x (PERMANENT FAILURE)
+### 3.2.5 5x (PERMANENT FAILURE)

 Status codes beginning with 5 are PERMANENT FAILURE status codes, meaning:

 The request has failed.  There is no response body.  The nature of the failure is permanent, i.e. identical future requests will reliably fail for the same reason.  The contents of  may provide additional information on the failure, and should be displayed to human users.  Automatic clients such as aggregators or indexing crawlers should not repeat this request.

-### 3.3.5 6x (CLIENT CERTIFICATE REQUIRED)
+### 3.2.5 6x (CLIENT CERTIFICATE REQUIRED)

 Status codes beginning with 6 are CLIENT CERTIFICATE REQUIRED status codes, meaning:

 The requested resource requires client-certificate authentication to access.  If the request was made without a certificate, it should be repeated with one.  If the request was made with a certificate, the server did not accept it and the request should be repeated with a different certificate.  The contents of  may provide additional information on certificate requirements or the reason a certificate was rejected.

-### 3.5.6 Notes
+### 3.2.6 Notes

 Note that for basic interactive clients for human use, errors 4 and 5 may be effectively handled identically, by simply displaying the contents of  under a heading of "ERROR".  The temporary/permanent error distinction is primarily relevant to well-behaving automated clients.  Basic clients may also choose not to support client-certificate authentication, in which case only four distinct status handling routines are required (for statuses beginning with 1, 2, 3 or a combined 4-or-5).

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