public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Edwin Amsler <edwinamsler@thinkboxsoftware•com>
To: git@vger•kernel.org
Subject: Git not using logged in user for propfind
Date: Tue, 29 Mar 2011 12:01:41 -0500	[thread overview]
Message-ID: <4D921075.1050208@thinkboxsoftware.com> (raw)

So, I set up a dandy non-ssl webshare on my server. SSL can come later 
once everything is configured right.

Git clones fine, but when it does a push and uses propfind, it decides 
to not use my username and so it gets a 401 not authorized error.

Here's output from my log. DAV works fine on everything I've tested on, 
it seems to be a git oopsie. Any ideas?

24.77.236.213 - -     [27/Mar/2011:18:21:47 -0500] "GET 
/dav/git/coral/info/refs?service=git-receive-pack HTTP/1.1" 401 409
24.77.236.213 - -     [27/Mar/2011:18:21:52 -0500] "GET 
/dav/git/coral/info/refs?service=git-receive-pack HTTP/1.1" 401 409
24.77.236.213 - edwin [27/Mar/2011:18:21:52 -0500] "GET 
/dav/git/coral/info/refs?service=git-receive-pack HTTP/1.1" 200 0
24.77.236.213 - edwin [27/Mar/2011:18:21:52 -0500] "GET 
/dav/git/coral/HEAD HTTP/1.1" 200 23
24.77.236.213 - -     [27/Mar/2011:18:21:52 -0500] "PROPFIND 
/dav/git/coral/ HTTP/1.1" 401 397

                 reply	other threads:[~2011-03-29 17:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4D921075.1050208@thinkboxsoftware.com \
    --to=edwinamsler@thinkboxsoftware$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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