From mboxrd@z Thu Jan  1 00:00:00 1970
From: luky-37 at hotmail.com (Lukas Tribus)
Date: Mon, 19 Jan 2015 14:22:45 +0100
Subject: setup issue: cgit only shows summary page
In-Reply-To: <2178822.XTAFUYKBoh@al>
References: <DUB123-W449DF317319A7785701FFAED4F0@phx.gbl>
 <20150116170545.GJ26383@serenity.lan>,<2178822.XTAFUYKBoh@al>
Message-ID: <DUB123-W37EDE93E0CCD4CBF027FFFED4A0@phx.gbl>

>> 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