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

Re: disabling PROPFIND when using smart http

From
ILIlari Liusvaara <ilari.liusvaara@elisanet.fi>
Date
Nov 23, 2010, 16:10 UTC
Message-ID
<20101123161018.GB10420@LK-Perkele-V2.elisa-laajakaista.fi>
In-Reply-To
<AANLkTikwqtPDDk6i0nMKJiXn5cc3DmTGYp0==daX96yd@mail.gmail.com>
On Tue, Nov 23, 2010 at 09:10:43PM +0530, Sitaram Chamarty wrote:
Show 12 quoted lines
> Hello,
> 
> Although smart http worked fine for me out of the box, following "man
> git-http-backend", I've found folks on #git for whom it seems to fail
> on doing a PROPFIND (found by setting GIT_CURL_VERBOSE=1).  Enabling
> WebDAV also doesn't seem to help, although that is quite likely to be
> some nuance in the Apache config I suppose.
> 
> The thing is, I *think* that PROPFIND is not, strictly speaking,
> needed when you use the smart HTTP mode.  If that is indeed true, can
> we stop git from even attempting it, and so avoid the need to setup
> WebDAV on Apache?

I thought that this is quite strange, and as consequence, decided to dig a bit.

This is pretty telling:

$ git grep -i --files-with-matches "propfind" http-push.c

http-push.c is AFAIK not used by smart HTTP, only by dumb HTTP push.

Apparently pusher is falling back to dumb WebDAV push for some reason. And then failing because server does not support it or isn't configured apporiately for it.

-Ilari
Previous: Sitaram ChamartyNext: Scott Chacon
Message 2 of 5 in “disabling PROPFIND when using smart http”
  1. Sitaram ChamartyNov 23, 2010
  2. Ilari LiusvaaraNov 23, 2010
  3. Scott ChaconNov 23, 2010
  4. Sitaram ChamartyNov 23, 2010
  5. Scott ChaconNov 23, 2010

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.