From: Francis Galiegue <fg@one2team.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: "Alexander Gavrilov" <angavrilov@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC PATCH] gitweb: Support filtering projects by .htaccess files.
Date: Tue, 4 Nov 2008 08:42:26 +0100 [thread overview]
Message-ID: <200811040842.26710.fg@one2team.net> (raw)
In-Reply-To: <200811040124.36708.jnareb@gmail.com>
Le mardi 04 novembre 2008, Jakub Narebski a écrit :
[...]
> >
> > As to what repository is accessible to whom, does gitweb really have
> > an internal mechanism for this? Wouldn't it be "better" is privately
> > accessible projects were available on another website to start with?
>
> The problem is that Apache has to decide whether to deny or grant access
> based on URL, not on path in filesystem. Perhaps that is possible...
>
It is, with <Location> or <LocationMatch>. You can use mod_access directives
within these (or mod_auth* ones).
--
Francis Galiegue, fg@one2team.com
[ATTENTION - CHANGEMENT D'ADRESSE !]
40 av Raymond Poincaré, 75016 PARIS
+33178945570, +33683877875
next prev parent reply other threads:[~2008-11-04 7:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 16:43 [RFC PATCH] gitweb: Support filtering projects by .htaccess files Alexander Gavrilov
2008-11-03 16:54 ` Francis Galiegue
2008-11-03 17:26 ` Alexander Gavrilov
2008-11-03 17:45 ` Francis Galiegue
2008-11-03 18:18 ` Jakub Narebski
2008-11-03 18:44 ` Francis Galiegue
2008-11-03 19:17 ` Jakub Narebski
2008-11-03 21:59 ` Francis Galiegue
2008-11-04 0:24 ` Jakub Narebski
2008-11-04 7:42 ` Francis Galiegue [this message]
2008-11-03 22:57 ` Jakub Narebski
2008-11-05 22:36 ` Alexander Gavrilov
2008-11-05 23:26 ` Jakub Narebski
2008-11-06 19:43 ` Alexander Gavrilov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200811040842.26710.fg@one2team.net \
--to=fg@one2team.net \
--cc=angavrilov@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.