=> Re: "Definitively can't pack entire documentation into my head:..." | In: s/Gemini
Yes, responses with status code 20 need to include the MIME type of the content. The specification does not make that optional.
The client is not expected to make any guesses based on file extension. That wouldn't even work in cases where the URL has no extension.
I've seen some (old? broken?) server implementations that send a plain "20 " as a response, which has led me to fall back to a default MIME type of "text/gemini; charset=utf-8" in Lagrange, but it's perfectly acceptable for a client to reject such responses as invalid, IMO.
2024-12-02 · 2 months ago
=> 👻 ps [OP] · Dec 02 at 12:36:
Agreed, if that's not my specification misunderstand, will not apply any extra action on client side so, but make some notice and maybe append binary download option at this moment. Thanks for confirmation!
=> 🌒 s/Gemini
Definitively can't pack entire documentation into my head: must server append content mime type to all 20 status codes? Or that is optional, and client should resolve content type by it extension (when not provided by server)
=> 💬 ps · 2 comments · 2024-12-02 · 2 months ago This content has been proxied by September (3851b).Proxy Information
text/gemini; charset=utf-8