From: "Jason Wagner" <jason@nialscorva.net>
To: git@vger.kernel.org
Subject: Git over HTTPS
Date: Sun, 01 Feb 2009 15:55:50 -0400 [thread overview]
Message-ID: <20090201195550.9011.qmail@server262.com> (raw)
I'm trying to set up a git repository on DAV on Apache, but having some trouble pushing via HTTPS. I've set everything up according to the documentation-- http.sslVerify=false, .netrc setup, bare repository and update-server-info, etc. The goal is to have read access available by http, but require authed https to write. Here's the config I've been using:
Alias /public.git /var/git/public
<Location /public.git>
DAV on
Options +Indexes
#TEST <LimitExcept GET PROPFIND OPTIONS>
#TEST AuthType Basic
#TEST AuthName "Git repository"
#TEST AuthUserFile /var/git/public.git.httpusers
#TEST Require valid-user
#TEST SSLRequireSSL
#TEST </LimitExcept>
</Location>
I turned off the LimitExcept for testing purposes. Inside of public is "logging", a git init --bare repository. When testing, I can do the following:
git config repository.http.url http://jason@platinum/public.git/logging
git config repository.https.url https://jason@platinum/public.git/logging
git pull http
git push http
# fresh local repository
git pull https
When I do "git push https -f --all -v" after changing a single file, I get:
Pushing to https://jason@platinum/public.git/logging
Getting pack list
Fetching remote heads...
refs/
refs/heads/
refs/tags/
updating 'refs/heads/master'
from b8339306a895f5f18675116ab202b001cfbb95ce
to 00d2d209b62f6f5322e943726b90bbf75f8a940a
Then it freezes until I ctrl-c it. Sometimes the process stays around afterwards sometimes and needs a kill -9.
In the apache logs, I see the same requests coming in on both the http and https pushes. It seems to be locking on
[01/Feb/2009:14:36:05 -0500] 127.0.0.1 TLSv1 RC4-MD5 "MKCOL /public.git/logging/refs/ HTTP/1.1" 321
or
[01/Feb/2009:08:43:51 -0500] 127.0.0.1 TLSv1 RC4-MD5 "UNLOCK /public.git/logging/info/refs HTTP/1.1" -
I've done this on both git 1.5.6.6 and 1.6.2 to the same results. I'm using a fully updated Fedora 9 install on the server machine. Has anyone run into similar problems or have any suggestions?
---
Jason Wagner
reply other threads:[~2009-02-01 20:03 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=20090201195550.9011.qmail@server262.com \
--to=jason@nialscorva.net \
--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 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.