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

Re: git-http-push / webDAV

From
EREygene Ryabinkin <rea-git@codelabs.ru>
Date
Oct 2, 2007, 08:54 UTC
Message-ID
<20071002085416.GW975@void.codelabs.ru>
In-Reply-To
<47020603.3080000@jentro.com>
Thomas, good day.
Tue, Oct 02, 2007 at 10:49:07AM +0200, Thomas Pasch wrote:
> I've investigated my problem a little further. The nasty
> 'UNLOCK HTTP error 400' has come from a proxy that
> doesn't accept webDAV stuff. Thus I unset the 'http_proxy'
> env variable (looks like cadaver hasn't cared...).
Yep, proxies can be tricky with the DAV stuff.
Show 10 quoted lines
> However, the main problem still remains. Using a non empty
> remote http repo, modifying and committing, then:
> 
> > git push -v
> Pushing to http://test@x.x.x.x/git/git.git
> 
> still waits for a long time and finally:
> 
> Error: no DAV locking support on remote repo http://test@x.x.x.x/git/git.git
> error: failed to push to 'http://test@x.x.x.x/git/git.git'

Try using URL with the slash at the end, like 'http://test@x.x.x.x/git/git.git/'. This should help.

-- 
Eygene
Previous: Thomas PaschNext: Thomas Pasch
Message 4 of 8 in “git-http-push / webDAV”
  1. Thomas PaschOct 1, 2007
  2. Eygene RyabinkinOct 1, 2007
  3. Thomas PaschOct 2, 2007
  4. Eygene RyabinkinOct 2, 2007
  5. Thomas PaschOct 2, 2007
  6. Eygene RyabinkinOct 2, 2007
  7. Thomas PaschOct 2, 2007
  8. Thomas PaschOct 9, 2007

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.