[Tech] Useless statistics of the day: status codes

Sean Conner sean at conman.org
Mon Jan 4 19:16:01 GMT 2021
It was thus said that the Great Stephane Bortzmeyer once stated:
> 
> The rest is marginal, less than ten URI:
> 
> 49 : First status code I find which is not in the official
> specification. Anyone has an idea? Two URI.
> 2 : Old server with the deprecated one-digit status codes?
> 39 : Not in the official specification. Anyone has an idea? Two URI.
> 59 : Bad request (no idea why my client sends bad requests)
> 99 : Not in the official specification. Anyone has an idea? Two URI.
> 58 : Not in the official specification. Anyone has an idea? Two URI.
> 29 : Not in the official specification. Anyone has an idea? Two URI.
> 43 : Proxy error. Reason unknown.
> 61 : Certificate not authorised. Since I do not send client
> certificates, this is surprising.
> 41 : Server not available (maintenance, for instance).
> 52 : Gone. Like 51 but final. Just one URI,
> <gemini://gemini.conman.org/no-longer-here/> so it's probably a test.
> 22 : Not in the official specification. Anyone has an idea? One URI.
> 69 : Not in the official specification. Anyone has an idea? One URI.
> 19 : Not in the official specification. Anyone has an idea? One URI.
> 
> The number of status codes not registered in the specification may
> mean that some servers are extending the Gemini protocol with unused
> status codes. But some are also in test capsules like
> <gemini://gemini.conman.org/> or <gemini://egsam.glv.one/>.

  The Gemini Client Torture Test [1] is responsible for the following
erroneous status codes:

	99, 29, 39, 49, 58, 2, and 0.

  I know there's another client test out there, so it could be that as well.

  -spc

[1]	gemini://gemini.conman.org/test/torture/


Archive home | About this archive