From: Jeff King <peff@peff.net>
To: Jason Pyeron <jpyeron@pdinc.us>
Cc: 'git' <git@vger.kernel.org>
Subject: Re: Trying to understand the web dav details
Date: Sat, 5 Jan 2013 23:19:42 -0500 [thread overview]
Message-ID: <20130106041942.GB4879@sigill.intra.peff.net> (raw)
In-Reply-To: <151C51E6FBD848739A43A2C17D78DD68@black>
On Sat, Jan 05, 2013 at 08:32:09PM -0500, Jason Pyeron wrote:
> When doing a clone by https (reverse proxied to http) the first request is
>
> GET /git/project/info/refs?service=git-upload-pack
>
> How does the ?service=xxxx get translated in to the action performed on the web
> server?
If you are using the git-http-backend CGI, it will interpret the service
tag and start smart-http. See "git help http-backend" for details on
plugging it into Apache.
Cloning/fetching does not use DAV at all; it is only for non-smart
pushing (and I would not recommend setting it up; the smart protocol
spoken by git-http-backend does pushing much more efficiently, and is
better maintained).
> I ask because I have 2 projects, one works the other does not.
>
> I am using httpd-2.0.52-49.ent.centos4 and git-1.7.9.6-1.
>
> I am not even sure what to tell more about or where to look next.
If you haven't set up git-http-backend, then git is just going to fetch
the remote repo's data directly over http. So the usual advice for
accessing something via http would apply (check the server's access and
error logs, try hitting it with a web browser, etc).
If you set GIT_CURL_VERBOSE=1 in your environment, git will spew a lot
of debugging information about what http requests it is making. That
might give you a clue (you haven't said anything about what does not
work, so I can't be more specific).
-Peff
next prev parent reply other threads:[~2013-01-06 4:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-06 1:32 Trying to understand the web dav details Jason Pyeron
2013-01-06 4:19 ` Jeff King [this message]
2013-01-06 4:49 ` Pyeron, Jason J CTR (US)
2013-01-06 5:38 ` Jeff King
2013-01-06 6:20 ` Jason Pyeron
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=20130106041942.GB4879@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=jpyeron@pdinc.us \
/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).