Re: git through http (or https)

[Mark Wielaard <mark@klomp.org>]

On Thu, Jan 05, 2017 at 03:25:01PM -0500, Frank Ch. Eigler wrote:
> > [...]  Yes, that is what the rewrite rules would fix.  If you enable
> > the rules in htdocs/git/.htaccess [...]
> 
> I put you on the fileacl for /sourceware/www/sourceware/htdocs/git/.htaccess
> to play (carefully) with.  It may not be quite so easy due to our symlinks
> and various group permissions.

You are right. It isn't simple because of the symlinks inside the directory
which seem to get resolved/matched/rewritten before/after any explicit
rewrite rule. In the end the best I could come up with was the following.
It makes sure the "advertised" http[s]://sourceware.org/git/foobar.git
links resolve. But they don't result in "pretty" URLs. I do think it is
better than the current Forbidden results though.

# This seems to be the best we can do given directory/.htaccess rewrite rules
# do get rewritten/matched themselves before/after the rewrite rules even if
# we use the [L] flag. So we match on the ending '/' that comes from following
# the symlink to the underlying directory. Then we do a browser [R]edirect so
# that the results doesn't get rewritten/matched again. This at least rewrite
# the user visible http://sourceware.org/git/foobar.git URLs to something that
# isn't Forbidden (the underlying git directory).
RewriteEngine on
RewriteBase /git/
RewriteRule ^([a-zA-Z/_-]+\.git)/$ ?p=$1 [R,L]

I believe the above is safe and keeps everything working as intended.
But please feel free to revert/remove the rewrite rule if it doesn't
or if you are afraid it might conflict with something.

Thanks,

Mark