Proposal about content-size and hash
John Cowan
cowan at ccil.org
Mon Nov 2 12:52:06 GMT 2020
This is wonderful and just what I need for Dioscuri, which needs to be able
to return new content as the URL where it is now stored. I was going to do
that with a new response code, but this is much better.
The Dioscuri spec is at <tinyurl.com/dioscuri-spec>. Reviews are
welcome. And it does include content-length, because TLS 1.2 is not able
to close just one side of a connection.
On Mon, Nov 2, 2020 at 5:54 AM Petite Abeille <petite.abeille at gmail.com>
wrote:
>
>
> > On Nov 1, 2020, at 15:47, Solderpunk <solderpunk at posteo.net> wrote:
> >
> > I've explained in another email why I don't think it's okay to put this
> > information into the MIME type.
>
> Actually, one could use a Message/External-Body content type, sporting a
> SIZE parameter, e.g:
>
> message/external-body; access-type=URL; URL="gemini://example.com/foo";
> SIZE=1024
>
> could != should :D
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201102/6bbba2a0/attachment.htm>
More information about the Gemini
mailing list