💾 Archived View for rawtext.club › ~sloum › geminilist › 001748.gmi captured on 2020-10-31 at 02:29:43. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
solderpunk solderpunk at SDF.ORG
Tue Jun 16 21:00:14 BST 2020
- - - - - - - - - - - - - - - - - - -
On Tue, Jun 16, 2020 at 08:21:51PM +0100, Luke Emmet wrote:
So what I think we need is something around HTTP 0.95 (it never existed)
which is about half way between HTTP 0.9 and 1.0.
GET (gemini right now)
POST (for non-idempotent interactions)
Content-Length indicator (to make POST work)
no other headers, so not extensible, so not as far as HTTP 1.0, but allows
application development.
This sounds really nice (honestly!), but the big problem for me wasalways: how does the client tell the server if it's doing a GET or aPOST without the protocol including some kind of marker for this, whichcould then potentially get extended ad infinitum by people definingtheir own equivalents to HEAD and PUT and etc, etc? It's the usualtheme: if you have *one* of something, it can be implicit, and as suchnobody can try alternative values. As soon as you have two or more, youneed to tell the server about it, and then people can try telling itdifferent things, and before long there is more than just two...
Cheers,Solderpunk