Re: gitweb testing with non-apache web server

Jakub Narebski [off-list ref] writes:

Marc Singer wrote:

quoted

That isn't enough.  I did something like that when I was exploring the
script.  While the change *does* eliminate the 403 error, it doesn't
make the rest of the script work properly.  All of the links return to
the same page that lists the projects.

Strange... PATH_INFO is used _only_ if 'p' parameter is not set. And all
links use 'p=$project', not PATH_INFO...

Are you sure you did changes mentioned in earlier post?

Well, more importantly, why would we do something like this in the first 
place?

Wouldn't it be a lot better to just rip out PATH_INFO stuff,
especially since all pages the script generates use ?p=$project 
to pass that information around and never uses PATH_INFO?

Junio C Hamano wrote:

Jakub Narebski [off-list ref] writes:

quoted

Strange... PATH_INFO is used _only_ if 'p' parameter is not set. And all
links use 'p=$project', not PATH_INFO...

Are you sure you did changes mentioned in earlier post?

Well, more importantly, why would we do something like this in the first 
place?

Wouldn't it be a lot better to just rip out PATH_INFO stuff,
especially since all pages the script generates use ?p=$project 
to pass that information around and never uses PATH_INFO?

The PATH_INFO is here because it is easier to edit parameters by hand when
the most important one, the project to examine, can be passed as PATH_INFO.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git