Proposal about content-size and hash

[Philip Linde]

On Mon, 02 Nov 2020 18:54:32 +0000
prisonpotato at tilde.team wrote:

> a new response code, like 22: Response with size.
> 
> 20 text/gemini
> 22 100 text/gemini

The spec currently explicitly prohibits this kind of use of the status
codes, but it could be a new first-digit response code, e.g. 7x. This
would naturally take some time for the implementations to adopt.

I personally don't miss content-length in practice, but I think the
fact that it wasn't included in the protocol from the beginning is the
most compelling argument against it. That said, I'd happily implement,
something like a new status code to account for such a change in my
client. When would servers dare use it, though?

-- 
Philip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201102/fc048477/attachment.sig>