Content length, EOF -- ways to resolve whether we received everything

Nick Thomas gemini at ur.gs
Fri Oct 30 13:00:25 GMT 2020


On Fri, 2020-10-30 at 12:50 +0100, Björn Wärmedal wrote:
> 
> "But, ew0k! The <META> is for MIME types! That's not a MIME type!"

I predict this is not going to be popular ^^.

The HTTP approach to the specific problem of no content-length header
is (was) chunked transfer-encoding: 
https://en.wikipedia.org/wiki/Chunked_transfer_encoding

Perhaps signalling this is more acceptable in the <META> area?
Transfer-encoding is at least directly about the format of the returned
bytes.

Signalling support from the client side is more difficult, though. It
could be an opt-in thing with server-side state when authenticated, but
that's a bit niche.

I predict adding it as a requirement to the spec will not be popular
either ;).

/Nick




More information about the Gemini mailing list