Gemini transactions (was Re: Client behavior when server doesn't close connection?)

[Petite Abeille]

> On Jul 9, 2020, at 14:27, juhani <juhani at envs.net> wrote:
> 
> Comparison of tcp streams revealed
> that on the working sites the last packet from the server had FIN flag, and on
> the failing sites it didn't.

While at it, perhaps the spec should make closing the connection more prominent.

At the moment, it's shown in 1.1 Gemini transactions:

S:   Sends response header (one CRLF terminated line), closes connection
     under non-success conditions (see 3.1 and 3.2)
S:   Sends response body (text or binary data) (see 3.3)
S:   Closes connection

And mentioned in 3.1 Response headers:

If <STATUS> 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.

This could be perhaps reemphasized with:

If <STATUS> belongs to the "SUCCESS" range of code, then the server MUST close the connection after sending the header and response body.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20200709/241e8ae7/attachment.htm>