-- 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: 17e5289ae74b9b21ef9aa429fa669e33673c08bb: path_to: revision_to:
commit 17e5289ae74b9b21ef9aa429fa669e33673c08bb Author: Solderpunk <solderpunk@sdf.org> Date: Fri May 22 18:41:13 2020 +0000 Specify CRLF or LF line endings. diff --git a/docs/spec-spec.txt b/docs/spec-spec.txt
--- a/docs/spec-spec.txt +++ b/docs/spec-spec.txt @@ -206,6 +206,18 @@ Response bodies only accompany responses whose header indicates a SUCCESS status (i.e. a status code whose first digit is 2). For such responses, <META> is a MIME media type as defined in RFC 2046. +Internet media types are registered with a canonical form. Content +transferred via Gemini MUST be represented in the appropriate +canonical form prior to its transmission except for "text" types, as +defined in the next paragraph. + +When in canonical form, media subtypes of the "text" type use CRLF as +the text line break. Gemini relaxes this requirement and allows the +transport of text media with plain LF alone (but NOT a plain CR alone) +representing a line break when it is done consistently for an entire +response body. Gemini clients MUST accept CRLF and bare LF as being +representative of a line break in text media received via HTTP. + If a MIME type begins with "text/" and no charset is explicitly given, the charset should be assumed to be UTF-8. Compliant clients MUST support UTF-8-encoded text/* responses. Clients MAY optionally
-----END OF PAGE-----
-- Response ended
-- Page fetched on Sun Jun 2 19:11:30 2024