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: Mon, 3 Nov 2008 19:44:02 +0100 [thread overview]
Message-ID: <200811031944.03116.fg@one2team.net> (raw)
In-Reply-To: <m38ws0fzca.fsf@localhost.localdomain>
Le Monday 03 November 2008 19:18:56 Jakub Narebski, vous avez écrit :
> >
> > Well, as far as Apache is concerned, it can do:
> >
> > * basic .htpasswd authentication,
> > * LDAP,
> > * PAM,
> > * SSL certificate check (via mod_ssl),
> > * probably others.
> >
> > Plenty of possibilities.
> [...]
>
> Well, the question is if Apache (and other web servers used with
> gitweb) can do authentication based on path_info or on query-string.
> Because it is encoded in gitweb (via $projectroot) where to find git
> repositories...
>
Can you expand on path_info and query-string? Keep in mind that Apache
has mod_rewrite, which can rewrite URLs in any way before it gets
actually sent to the underlying program (whether it be a CGI or
anything else), even badly (or mischievously).
--
fge
next prev parent reply other threads:[~2008-11-03 18:46 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 [this message]
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
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=200811031944.03116.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.