>> 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 _______________________________________________ CGit mailing list [email protected] http://lists.zx2c4.com/mailman/listinfo/cgit
