From: luky-37 at hotmail.com (Lukas Tribus)
Subject: setup issue: cgit only shows summary page
Date: Mon, 19 Jan 2015 14:22:45 +0100 [thread overview]
Message-ID: <DUB123-W37EDE93E0CCD4CBF027FFFED4A0@phx.gbl> (raw)
In-Reply-To: <2178822.XTAFUYKBoh@al>
>> I think you either need to set PATH_INFO here *or* to avoid setting
>> SCRIPT_NAME. CGit uses SCRIPT_NAME to decide whether to use path URLs
>> or the "url=" query parameter. If it's using path URLs then you need to
>> have PATH_INFO specified as the full path (which must start with
>> $SCRIPT_NAME).
>>
>> Note that I've never used fcgiwrapper so I don't know whether it will
>> set either of those automatically; I'm just going on how CGit behaves.
>
> fcgiwrap uses SCRIPT_FILENAME (if set) and the concatenation of
> DOCUMENT_ROOT and SCRIPT_NAME otherwise.
>
> Suggestions for the nginx config: generally a default, sane set of
> fastcgi parameters is available in the fastcgi_params file which you can
> include with "include fastcgi_params;".
Thanks for these hints. In the end, I had to intercept the fcgi requests
to understand whats going on exactly, and I found that nginx' try_files
resets PATH_INFO [1].
Configuring:
?fastcgi_split_path_info ? ? ? ^(/cgit/)(.*)$;
?fastcgi_param PATH_INFO $fastcgi_path_info;
did the trick for me, without removing try_files.
Lukas
[1] http://trac.nginx.org/nginx/ticket/321
prev parent reply other threads:[~2015-01-19 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 16:30 luky-37
2015-01-16 17:05 ` john
2015-01-16 17:48 ` peter
2015-01-19 13:22 ` luky-37 [this message]
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=DUB123-W37EDE93E0CCD4CBF027FFFED4A0@phx.gbl \
--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).