Re: http-smart-backend: can clone, cannot push

From: Jeremiah Foster <jeremiah.foster@pelagicore.com>
Date: Jun 2, 2010, 15:16 UTC
Message-ID: <825A1E57-48AE-4BA5-AD5C-431DA8E959DA@pelagicore.com>
In-Reply-To: <20100601155833.GT16470@spearce.org>

On Jun 1, 2010, at 17:58, Shawn O. Pearce wrote:

Thanks Shawn, and everyone else who commented on this thread - I appreciate the help.

Show 12 quoted lines

> Jeremiah Foster <jeremiah.foster@pelagicore.com> wrote:
>> Maybe I _have_ to be authenticated since the documentation states:
>> "If the client is authenticated, thereceive-pack service is enabled,
>> which serves git send-pack clients, which is invoked from git push."
> 
> Yes.
> 
> A flaw of the smart HTTP transport is the servers are
> nearly impossible to configure for anonymous clone and
> authenticated push via the same URL.  The servers just
> can't seem to be configured to require authentication
> for the $GIT_DIR/info/refs?service=git-receive-pack request.

I created a system to authenticate and then I could push and pull with the same URL. Thanks again for the help and I'm going to try to write up a short blog post about using this because I think it is a really great way to share git repos.

Jeremiah