From: John Keeping <firstname.lastname@example.org>
To: Andreas Mahling <email@example.com>
Subject: Re: cgit with busybox httpd
Date: Mon, 6 Mar 2023 11:41:18 +0000 [thread overview]
Message-ID: <ZAXRXhaQWyHwR4tv@keeping.me.uk> (raw)
On Mon, Mar 06, 2023 at 11:13:10AM +0100, Andreas Mahling wrote:
> I'm in the process to configure a cgit instance for my private network at home.
> Because my internet router will be the host for git and cgit, I'm
> looking for a ligthweight setup.
> I would like to use busybox httpd as webserver, which has a very low
> footprint and supports cgi, but no other fancy bells and whistles,
> especially no url rewrite.
> It works in principle, but there is a problem with the URLs generated
> by cgit: they seem always containing a trailing slash. This leads to a
> 404 error thrown by httpd. If I manually remove the slash, everyting
> is OK.
> Example given:
> http://git/cgi-bin/cgit.cgi/linuxadmin.git/ -> 404
> http://git/cgi-bin/cgit.cgi/linuxadmin.git -> Page ist shown
> Is there a way to tell cgit to give up the trailing slash? I'm running
> cgit-1.2.3-r3 on Alpine 3.17.2
I don't think it's possible to change that behaviour without patching
CGit. Given how URLs are constructed, it looks a bit complicated to fix
in all cases, but you could remove the setting of "virtual_root" in
cmd_main() to force using query parameters instead of virtual paths in
Can you tell where the 404 is generated? Is this a case of httpd
returning an error when it shouldn't, or is it a behaviour difference
that CGit isn't handling correctly - maybe other CGI hosts strip
trailing slashes before passing a path to CGit but httpd doesn't?
next prev parent reply other threads:[~2023-03-06 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 10:13 Andreas Mahling
2023-03-06 11:41 ` John Keeping [this message]
[not found] ` <CAF6j0WAEvS4AeX-pjEOnytt5SQ8vbguOhjX6VmVxEJ8rJ0x9rA@mail.gmail.com>
2023-03-06 14:42 ` John Keeping
2023-03-07 19:16 ` Andreas Mahling
2023-03-06 14:31 Andreas Mahling
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).