Proposal about content-size and hash

[Sean Conner]

It was thus said that the Great Arav K. once stated:
> Hi, Gemini peoples!
> 
> I have two main proposals for getting information like content-size
> (which, as has been discussed previously, would be very useful for even
> slightly big responses).
> 
> 1. Define specific additional MIME type parameters.  For example, one
>    could return '20 application/gzip; content-size=42069420' as the
>    response line.  This could also be used for giving the client a hash
>    of the data (parameter name e.g. 'content-hash-sha256'), useful for
>    verification and for checking against local caches of the same page.

  Ah yes ... this is something I proposed back in August of 2019:

	gemini://gemini.conman.org/gRFC/0003

  Solderpunk has always rejected it when it comes up, mumbling "simplicity"
and "not HTTP again" under his breath.  Another issue with this is that the
server might not know how big a given response is---think dynamic output
(via CGI/SCGI or similar).  It would have to be optional in any case.

> 2. Define an additional endpoint for retrieving meta info.

  I also proposed something along these lines in August of 2019:

	https://lists.orbitalfox.eu/archives/gemini/2019/000016.html

  Read the thread to see how that turned out.

  -spc