[spec] Adapting the HTTP Common Logging Format for use by Gemini servers

Sean Conner sean at conman.org
Sun Dec 27 23:12:19 GMT 2020


It was thus said that the Great Solderpunk once stated:
> 
> For the record, I don't like that the Apache format uses spaces as a
> field separator when spaces also occur inside the date.  Molly Brown's
> log format uses tabs as separators, so it works very nicely with the
> standard `cut` utility.  I use `cut`, `grep`, `sort`, `uniq` and `wc -l`
> in short pipelines to run queries on my logs, and really enjoy being
> able to do so.

  My own logging format is:

	remote=XXX.XXX.XXX.XXX status=20 request="gemini://gemini.conman.org/boston/2001/11/13.1" bytes=1540 subject="" issuer=""

(I've redacted the IP address)

  The final two fields record information about the client certificate to
help debug issues with my server.  Here's an example:

	remote=XXX.XXX.XXX.XXX status=20 request="gemini://gemini.conman.org/private/" bytes=333 subject="/CN=default" issuer="/CN=default"

  I did not change the subject or issuer.  It's been interesting to see
what's being sent in client certificates.

  -spc


More information about the Gemini mailing list