Subject: thttpd trimming terminating slashes
Date: Thu, 31 Jan 2019 12:07:53 +0000 [thread overview]
Message-ID: <d95a46fa189d4005d6f9cb565b0027467db3eed7.camel@aegee.org> (raw)
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
?????
reply other threads:[~2019-01-31 12:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d95a46fa189d4005d6f9cb565b0027467db3eed7.camel@aegee.org \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).