git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: Magnus Therning <magnus@therning.org>, git@vger.kernel.org
Subject: Re: [PATCH 2/2] doc/http-backend: give some lighttpd config examples
Date: Thu, 11 Apr 2013 13:02:33 -0400	[thread overview]
Message-ID: <20130411170233.GB1255@sigill.intra.peff.net> (raw)
In-Reply-To: <5166E935.2080206@gmail.com>

On Thu, Apr 11, 2013 at 06:47:49PM +0200, Jakub Narębski wrote:

> W dniu 11.04.2013 05:36, Jeff King napisał:
> 
> > +Note that unlike the similar setup with Apache, we can easily match the
> > +query string for receive-pack, catching the initial request from the
> > +client. This means that the server administrator does not have to worry
> > +about configuring `http.receivepack` for the repositories (the default
> > +value, which enables it only in the case of authentication, is
> > +sufficient).
> 
> Perhaps it would be worth including for Apache2 beside basic setup that
> requires http.receivepack set to true, also one like for LigHTTPd, i.e.
> 
>   RewriteCond %{QUERY_STRING} =service=git-receive-pack [OR]
>   RewriteCond %{REQUEST_URI} /git-receive-pack$
>   RewriteRule (.*) $1 [E=AUTHREQUIRED:yes]
> 
>   <Location /gitweb/>
>       Order Deny,Allow
>       Deny from env=AUTHREQUIRED
> 
>       AuthType Basic
>       AuthName "Git Access"
>       Require group committers
> 
>       Satisfy Any
>   <Location>
> 
> And perhaps also adding it as test...

That was the "I am not clever nor interested in Apache enough to figure
out how to do this..." part that I wrote. I have no clue if the above
works, but I'd be happy if you wanted to test it out and submit it as a
patch on top (I think it could even replace my 1/2, as making it just
work is a much better solution than having to explain the extra step in
the documentation).

-Peff

> -- 
> Jakub Narębski

  reply	other threads:[~2013-04-11 17:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09  5:45 git-http-backend: anonymous read, authenticated write Magnus Therning
2013-04-09 12:24 ` Jakub Narębski
2013-04-10 20:53   ` Magnus Therning
2013-04-09 17:12 ` Jeff King
2013-04-10 20:45   ` Magnus Therning
2013-04-10 21:53     ` Jeff King
2013-04-10 21:30   ` Jakub Narębski
2013-04-10 21:47     ` Jeff King
2013-04-10 23:19       ` Magnus Therning
2013-04-11  1:56         ` Jeff King
2013-04-11  3:30           ` [PATCH 0/2] http-backend documentation examples Jeff King
2013-04-11  3:32             ` [PATCH 1/2] doc/http-backend: clarify "half-auth" repo configuration Jeff King
2013-04-11  6:57               ` Magnus Therning
2013-04-11  3:36             ` [PATCH 2/2] doc/http-backend: give some lighttpd config examples Jeff King
2013-04-11 16:47               ` Jakub Narębski
2013-04-11 17:02                 ` Jeff King [this message]
2013-04-11 18:27                   ` Jakub Narębski
2013-04-13  3:33                   ` [PATCH 3/2] doc/http-backend: match query-string in apache half-auth example Jeff King
2013-04-13  8:52                     ` Jakub Narębski
2013-04-11  6:52           ` git-http-backend: anonymous read, authenticated write Magnus Therning
2013-04-11 19:34             ` Jeff King
2013-04-12  7:22               ` Magnus Therning
2013-04-11 16:43           ` Jakub Narębski

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=20130411170233.GB1255@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=magnus@therning.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).