Comment by 🥬 lamb-duh
Re: "I'm puzzeled. I see in my logs requests to my Gemini server…"
I just came across
A torture test for gemini servers.
[...]
Supported Tests
[...]
[URLEmpty]
Empty URLs should not be accepted by the server.
you should be able to figure out if this tool is making those requests by looking for the other tests the suite performs
May 03 · 4 days ago
4 Later Comments ↓
👽 spc476 [OP] · May 04 at 08:22:
It's a test to run against a server. You run it against the server you are writing to see if it handles things properly, not against an existing server unless you want to piss the operator off.
And yes, my server properly handles empty requests---it's the damn clients that are buggy.
yeah, I understand what it is.. it's a program that, among other things, does exactly what you're experiencing. anyone could run it against your server, if they wanted to, maybe without even wanting to piss you off.
And yes, my server properly handles empty requests---it's the damn clients that are buggy.
Does it? what *is* the proper way to handle an empty request?
👽 spc476 [OP] · May 04 at 20:56:
To return an error. What I'm ranting about are the clients that insist on sending an empty request when it isn't allowed by the Gemini specification, which, if the clients I see hitting my server are to go by, rival the HTTP specification in complexity.
okay, i misunderstood then. i thought you were interested in where those requests were coming from.
Original Post
I'm puzzeled. I see in my logs requests to my Gemini server that are empty. For gopher, an empty request is legal, and refers to the top page of a gopher server. I don't see where that's allowed in Gemini. If it is, can someone point to the chapter and verse where it's allowed? It's not like the Gemini specification is all that complicated.