Browse Source

gitweb/README: fix AliasMatch in example

When combining "dumb client" and human-friendly access by using the
'.git' extension to switch between the two, make sure the AliasMatch
covers the entire request. Without a full match, a request for

http://git.example.com/project/shortlog/branch..gitsomething

would result in a 404 because the server would try to access the
the project 'project/shortlog/branch.'

The solution is still not bulletproof, so document the possible failing
case.

Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
maint
Giuseppe Bilotta 16 years ago committed by Junio C Hamano
parent
commit
1bed73c64a
  1. 10
      gitweb/README

10
gitweb/README

@ -377,7 +377,7 @@ named without a .git extension (e.g. /pub/git/project instead of @@ -377,7 +377,7 @@ named without a .git extension (e.g. /pub/git/project instead of

DocumentRoot /var/www/gitweb

AliasMatch ^(/.*?)(\.git)(/.*)? /pub/git$1$3
AliasMatch ^(/.*?)(\.git)(/.*)?$ /pub/git$1$3
<Directory /var/www/gitweb>
Options ExecCGI
AddHandler cgi-script cgi
@ -402,6 +402,14 @@ http://git.example.com/project @@ -402,6 +402,14 @@ http://git.example.com/project

will provide human-friendly gitweb access.

This solution is not 100% bulletproof, in the sense that if some project
has a named ref (branch, tag) starting with 'git/', then paths such as

http://git.example.com/project/command/abranch..git/abranch

will fail with a 404 error.



Originally written by:
Kay Sievers <kay.sievers@vrfy.org>

Loading…
Cancel
Save