From: "aaron smith" <beingthexemplarylists@gmail.com>
To: git@vger.kernel.org
Subject: Re: git push over http - curl PUT error?
Date: Wed, 31 Dec 2008 05:29:53 -0800 [thread overview]
Message-ID: <d7ac1a680812310529p6b7e8d88r69755887304d3436@mail.gmail.com> (raw)
In-Reply-To: <d7ac1a680812310210r25795e66x35601059103892d7@mail.gmail.com>
ok, duh, i had to use git http-push. What is the difference? Thanks.
On Wed, Dec 31, 2008 at 2:10 AM, aaron smith
<beingthexemplarylists@gmail.com> wrote:
> hey all,
>
> I have one last issue to figure out with git over HTTP. This one is
> seriously stumping me.
>
> I have a bare git repository here: http://codeendeavor.com/guttershark.git/
>
> And I have a local git repo with some files in it, ready to push to
> this public one.
>
> Here's what I do to push to it:
>
> $git push origin master
>
> I then get this output:
> ""
> Fetching remote heads...
> refs/
> refs/heads/
> refs/tags/
> updating 'refs/heads/master'
> from a08e614723ff57047522511a2130d53010ebe0ca
> to 2db4bca0d137f4099973387472cf1666d0290e03
> sending 3 objects
> done
> Updating remote server info
> PUT error: curl result=22, HTTP code=403
> """
>
> I'm not sure how to get around this.
>
> The git repo permissions are 777, with owner/group apache:apache. I
> have DAV on, and the DavLockDB directive. which seems to all be ok.
> And I don't have any http authentication on it.. or access control
> list for that matter.
>
> Any ideas? Thanks All!
>
prev parent reply other threads:[~2008-12-31 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 10:10 git push over http - curl PUT error? aaron smith
2008-12-31 13:29 ` aaron smith [this message]
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=d7ac1a680812310529p6b7e8d88r69755887304d3436@mail.gmail.com \
--to=beingthexemplarylists@gmail.com \
--cc=git@vger.kernel.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).