💾 Archived View for gemi.dev › gemini-mailing-list › 000264.gmi captured on 2024-03-21 at 17:15:17. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2023-12-28)

-=-=-=-=-=-=-

(A little) Ambiguity in the response header specification

1. Baschdel (baschdel (a) disroot.org)

Hello [?].

Section 3.1 of the Gemini specification says that <STATUS> and <META> 
are separated by a single space character.

 > Gemini response headers look like this:
 >
 > <STATUS><SPACE><META><CR><LF>
 >
 > [?]
 >
 > <STATUS> and <META> are separated by a single space character.

The problem is the following:

Most people would read this as an ascii space character, however for 
some people this also includes a tab characters (and in my opinion they 
are not wrong)

For this reason I suggest to clarify by adding a line that states that 
<SPACE> refers to the ascii character 0x20 (because that is used by 
almost all servers already) (or if we want to allow tabs clearly specify 
that)

Have a nice Evening!
- Baschdel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20200630/129c
f901/attachment.htm>

Link to individual message.

2. solderpunk (solderpunk (a) SDF.ORG)

On Tue, Jun 30, 2020 at 10:35:08PM +0200, Baschdel wrote:
 
> For this reason I suggest to clarify by adding a line that states that
> <SPACE> refers to the ascii character 0x20 (because that is used by almost
> all servers already) (or if we want to allow tabs clearly specify that)

I have clarified this just now - sorry for forgetting to respond to your
earlier message about this on Mastodon!

Cheers,
Solderpunk

Link to individual message.

---

Previous Thread: Gemini Text Markup Language specification

Next Thread: [ANN] tinmop update