List for cgit developers and users
 help / color / mirror / Atom feed
From: Andreas Mahling <andreas.mahling@googlemail.com>
Cc: cgit@lists.zx2c4.com
Subject: Re: cgit with busybox httpd
Date: Tue, 7 Mar 2023 20:16:35 +0100	[thread overview]
Message-ID: <CAF6j0WAY0gb_Y91D-nQNDz=6HGZfwoF9AJVvom--dL_gW6NhYQ@mail.gmail.com> (raw)
In-Reply-To: <ZAX71kWRROjgpoVz@keeping.me.uk>

I've preferred to patch busybox httpd.
http://lists.busybox.net/pipermail/busybox/2023-March/090197.html

thanks for your help
Andreas
Am Mo., 6. März 2023 um 15:42 Uhr schrieb John Keeping <john@keeping.me.uk>:
>
> [Cc: add the mailing list back in]
>
> On Mon, Mar 06, 2023 at 01:01:50PM +0100, Andreas Mahling wrote:
> > It seems the 404 is generated by httpd, I think because the url ends with a
> > slash httpd treats the part after cgit.cgi not as PATH_INFO (as it should)
> > but as a directory. So this seems more a fault of httpd to me.
> >
> > Sorry, but I don't understand how to put into QUERY_STRING what now goes
> > into PATH_INFO. Do you mean the virtual-root option in cgitrc?
> > It is already commented out in my setup, but cgit builds the url with
> > PATH_INFO part anyway.
>
> To disable that feature you would have the patch the CGit source and
> build your own cgit binary.
>
> There is code in cmd_main() which automatically calculates the virtual
> root from other environment variables if they are provided (and it seems
> that httpd does provide this detail to CGI scripts).
>

  reply	other threads:[~2023-03-07 19:17 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
     [not found]   ` <CAF6j0WAEvS4AeX-pjEOnytt5SQ8vbguOhjX6VmVxEJ8rJ0x9rA@mail.gmail.com>
2023-03-06 14:42     ` John Keeping
2023-03-07 19:16       ` Andreas Mahling [this message]
2023-03-06 14:31 Andreas Mahling

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='CAF6j0WAY0gb_Y91D-nQNDz=6HGZfwoF9AJVvom--dL_gW6NhYQ@mail.gmail.com' \
    --to=andreas.mahling@googlemail.com \
    --cc=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).