From mboxrd@z Thu Jan  1 00:00:00 1970
From: dilyan.palauzov at aegee.org (=?UTF-8?Q?=D0=94=D0=B8=D0=BB=D1=8F=D0=BD_?= =?UTF-8?Q?=D0=9F=D0=B0=D0=BB=D0=B0=D1=83=D0=B7=D0=BE=D0=B2?=)
Date: Thu, 31 Jan 2019 12:07:53 +0000
Subject: thttpd trimming terminating slashes
Message-ID: <d95a46fa189d4005d6f9cb565b0027467db3eed7.camel@aegee.org>

To: Jef Poskanzer <jef at mail.acme.com>, webmaster at mail.acme.com,  thttpd at mail.acme.com
CC: cgit at lists.zx2c4.com

Hello,

after writing to thttpd-request at mail.acme.com , as suggested at http://www.acme.com/software/thttpd/, I get no replies. 
Therefore cannot subscribe to the mailing list thttpd at mail.acme.com, that was last used in 2014 according to 
https://marc.info/?l=thttpd&r=1&w=2 .

My experience with thttpd shows that it eliminates terminating slashes in the requests, before callnig a CGI program.

cgit (https://git.zx2c4.com/cgit/) insists of receivng a terminating slash, in order to always work correctly.  See the
discussion at https://lists.zx2c4.com/pipermail/cgit/2019-January/thread.html labelled ?Slash after /about?.

Please reach a consensus between cgit and thttpd whether a webserver is entitled to trim terminating slashes from the
URL.

Regards
  ?????