git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Trying to understand the web dav details

From
Jeff King <peff@peff.net>
Date
Jan 6, 2013, 05:38 UTC
Message-ID
<20130106053807.GA8551@sigill.intra.peff.net>
In-Reply-To
<871B6C10EBEFE342A772D1159D1320853A011871@umechphj.easf.csd.disa.mil>
On Sun, Jan 06, 2013 at 04:49:57AM +0000, Pyeron, Jason J CTR (US) wrote:
Show 8 quoted lines
> > > 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
> 
> No, using plain jane http and webdav. This server is not "allowed" to
> use cgi processes.

Then the service parameter should be ignored by your webserver, and it should just serve the info/refs file from the repository on the filesystem. And you are stuck using WebDAV for push.

> > GET /git/project-x/info/refs HTTP/1.1
> [...]
> * The requested URL returned error: 404 Not Found
Does the info/refs file exist in the project-x repository?
> fatal: https://server/git/project-x/info/refs not found: did you run git update-server-info on the server?
Did you?

If you can't run any git programs on the server at all (and it sounds like that may be the case), you'll need to run it locally before putting the repository data on the server.

Once you have WebDAV set up for pushing, it will update the info/refs file for each push. But if you are initially seeding the server with rsync or a tarfile, you'll want to make sure it has an up-to-date info/refs file.

-Peff
Previous: Pyeron, Jason J CTR (US)Next: Jason Pyeron
Message 4 of 5 in “Trying to understand the web dav details”
  1. Jason PyeronJan 6, 2013
  2. Jeff KingJan 6, 2013
  3. Pyeron, Jason J CTR (US)Jan 6, 2013
  4. Jeff KingJan 6, 2013
  5. Jason PyeronJan 6, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.