2 ms·
There's no content-length header in the response. The server has to close the connection to signal the end of the response body.
by Arnavion 6y ago
There's no content-length header in the response. The server has to close the connection to signal the end of the response body.
- woodruffw 6y ago> There's no content-length header in the response. I'm not sure I understand -- what's stopping me from adding one? One of Gemini's design goals seems to be client diversity and allowing clients to interpret responses on their own terms. Edit: To be even more explicit about it: the Gemini specification doesn't include any language that says that clients and servers MUST not use the "meta" field or their response bodies to negotiate additional functionality. The observation that nobody in the Gemini ecosystem currently does is tantamount to the observation that nobody has bothered to yet, just like with HTTP 1.0.
- Arnavion 6y ago>One of Gemini's design goals seems to be client diversity and allowing clients to interpret responses on their own terms. No, the design goal is the exact opposite of that. The protocol is intentionally designed to be non-extensible so that other features that go against its spirit are not added. You can of course add a content-length header to your server and write your own client that parses it, but you wouldn't be writing a Gemini server and client any more. https://gemini.circumlunar.space/docs/faq.gmi https://gemini.circumlunar.space/docs/faq.gmi goes in great length about this in section 2, and even specifically about (the lack of) content-length in section 2.12