threads / bug / 16991

http push to WebDAV server fails (apache 2.2 under Win) - possible bug!?

Subject: http push to WebDAV server fails (apache 2.2 under Win) - possible bug!?

## tl;dr

2 messages between Jan 5, 2009 and Feb 13, 2009.

replies: 1people: 2as markdown or json

Harald Weppner· Jan 5, 2009, 06:26 UTC · lore
Hi there,

just trying to get started to host a remote repository on a WebDAV share (served by apache2.2 on Windows). When I attempt to push from my local repository it indicates a 405 failure on a PUT of a *opaquelocktoken:* resource (cf. apache access log below). I don't know WebDAV in detail to know what's going wrong here but the colon in the resource name looks suspicious as it's not a permitted character under Windows. Could this indeed be a problem of not escaping the resource name properly?

Thanks & cheerio, Harry.
 > git push -v origin master
Pushing to http://user@example.com/webdav/repos/example.git/
Fetching remote heads...
   refs/
   refs/heads/
   refs/tags/
updating 'refs/heads/master'
   from 0000000000000000000000000000000000000000
   to   d310d475c459f7440a9a4ab8ae518f3a91011eb2
     sending 12 objects
PUT 9d68391c5426d3b3c69a6b4c43c1110d13a710d5 failed, aborting (22/405)
PUT 57964966cd88e6a3a61c46ed4b186f26d5133dab failed, aborting (22/405)
PUT 7e03ccd9dcbb5a2770cc5e52aa168a97897ce01b failed, aborting (22/405)
PUT 67d59f8095ad0b5d90b50b05634038c831871f05 failed, aborting (22/405)
PUT 726f7925fa8539c202558d1cf7567c173fed6b42 failed, aborting (22/405)
error: failed to push some refs to 'http://user@example.com/webdav/repos/example.git/'
Here's how the apache error log looks like

[Sun Jan 04 21:51:27 2009] [error] [client xxx.xxx.xx.xxx] File does not exist: C:/xampp/webdav/repos/example.git/info/refs [Sun Jan 04 21:51:27 2009] [error] [client xxx.xxx.xx.xxx] File does not exist: C:/xampp/webdav/repos/example.git/objects/info/packs

and this is apache's access log (showing the 405 errors)

[04/Jan/2009:21:51:26 -0800] "PROPFIND /webdav/repos/example.git/ HTTP/ 1.1" 207 588 "-" "git/1.6.1" [04/Jan/2009:21:51:27 -0800] "HEAD /webdav/repos/example.git/info/refs HTTP/1.1" 404 - "-" "git/1.6.1" [04/Jan/2009:21:51:27 -0800] "HEAD /webdav/repos/example.git/objects/ info/packs HTTP/1.1" 404 - "-" "git/1.6.1" [04/Jan/2009:21:51:27 -0800] "PROPFIND /webdav/repos/example.git/refs/ HTTP/1.1" 207 2637 "-" "git/1.6.1" [04/Jan/2009:21:51:27 -0800] "PROPFIND /webdav/repos/example.git/refs/ heads/ HTTP/1.1" 207 950 "-" "git/1.6.1" [04/Jan/2009:21:51:27 -0800] "PROPFIND /webdav/repos/example.git/refs/ tags/ HTTP/1.1" 207 950 "-" "git/1.6.1" [04/Jan/2009:21:51:27 -0800] "MKCOL /webdav/repos/example.git/refs HTTP/1.1" 301 433 "-" "git/1.6.1" [04/Jan/2009:21:51:28 -0800] "MKCOL /webdav/repos/example.git/refs/ HTTP/1.1" 405 1060 "-" "git/1.6.1" [04/Jan/2009:21:51:28 -0800] "MKCOL /webdav/repos/example.git/refs/ heads HTTP/1.1" 301 439 "-" "git/1.6.1" [04/Jan/2009:21:51:28 -0800] "MKCOL /webdav/repos/example.git/refs/ heads/ HTTP/1.1" 405 1060 "-" "git/1.6.1" [04/Jan/2009:21:51:28 -0800] "LOCK /webdav/repos/example.git/refs/ heads/master HTTP/1.1" 200 471 "-" "git/1.6.1" [04/Jan/2009:21:51:28 -0800] "PROPFIND /webdav/repos/example.git/ objects/d3/ HTTP/1.1" 404 1138 "-" "git/1.6.1" [04/Jan/2009:21:51:28 -0800] "PROPFIND /webdav/repos/example.git/ objects/24/ HTTP/1.1" 404 1138 "-" "git/1.6.1" [04/Jan/2009:21:51:28 -0800] "PROPFIND /webdav/repos/example.git/ objects/62/ HTTP/1.1" 404 1138 "-" "git/1.6.1" [04/Jan/2009:21:51:28 -0800] "PROPFIND /webdav/repos/example.git/ objects/ca/ HTTP/1.1" 207 950 "-" "git/1.6.1" [04/Jan/2009:21:51:28 -0800] "PROPFIND /webdav/repos/example.git/ objects/9c/ HTTP/1.1" 404 1138 "-" "git/1.6.1" [04/Jan/2009:21:51:29 -0800] "PROPFIND /webdav/repos/example.git/ objects/7e/ HTTP/1.1" 207 950 "-" "git/1.6.1" [04/Jan/2009:21:51:29 -0800] "PROPFIND /webdav/repos/example.git/ objects/6f/ HTTP/1.1" 404 1138 "-" "git/1.6.1" [04/Jan/2009:21:51:29 -0800] "PROPFIND /webdav/repos/example.git/ objects/72/ HTTP/1.1" 207 950 "-" "git/1.6.1" [04/Jan/2009:21:51:29 -0800] "PROPFIND /webdav/repos/example.git/ objects/67/ HTTP/1.1" 207 950 "-" "git/1.6.1" [04/Jan/2009:21:51:29 -0800] "PROPFIND /webdav/repos/example.git/ objects/57/ HTTP/1.1" 207 951 "-" "git/1.6.1" [04/Jan/2009:21:51:29 -0800] "PROPFIND /webdav/repos/example.git/ objects/9d/ HTTP/1.1" 207 950 "-" "git/1.6.1" [04/Jan/2009:21:51:29 -0800] "PUT /webdav/repos/example.git/objects/9d/ 68391c5426d3b3c69a6b4c43c1110d13a710d5_opaquelocktoken: 35019a69-7377-2545-a7fa-0f7888f6e3bc HTTP/1.1" 405 1058 "-" "git/1.6.1" [04/Jan/2009:21:51:29 -0800] "PUT /webdav/repos/example.git/objects/ 57/964966cd88e6a3a61c46ed4b186f26d5133dab_opaquelocktoken: 35019a69-7377-2545-a7fa-0f7888f6e3bc HTTP/1.1" 405 1058 "-" "git/1.6.1" [04/Jan/2009:21:51:29 -0800] "PUT /webdav/repos/example.git/objects/7e/ 03ccd9dcbb5a2770cc5e52aa168a97897ce01b_opaquelocktoken: 35019a69-7377-2545-a7fa-0f7888f6e3bc HTTP/1.1" 405 1058 "-" "git/1.6.1" [04/Jan/2009:21:51:29 -0800] "PUT /webdav/repos/example.git/objects/67/ d59f8095ad0b5d90b50b05634038c831871f05_opaquelocktoken: 35019a69-7377-2545-a7fa-0f7888f6e3bc HTTP/1.1" 405 1058 "-" "git/1.6.1" [04/Jan/2009:21:51:29 -0800] "PUT /webdav/repos/example.git/objects/ 72/6f7925fa8539c202558d1cf7567c173fed6b42_opaquelocktoken: 35019a69-7377-2545-a7fa-0f7888f6e3bc HTTP/1.1" 405 1058 "-" "git/1.6.1" [04/Jan/2009:21:51:30 -0800] "UNLOCK /webdav/repos/example.git/refs/ heads/master HTTP/1.1" 204 - "-" "git/1.6.1"

Johannes Schindelin· Feb 13, 2009, 02:14 UTC · re: Harald Weppner · lore

Re: http push to WebDAV server fails (apache 2.2 under Win) - possible bug!?

Hi,
On Sun, 4 Jan 2009, Harald Weppner wrote:
Show 7 quoted lines
> just trying to get started to host a remote repository on a WebDAV share 
> (served by apache2.2 on Windows). When I attempt to push from my local 
> repository it indicates a 405 failure on a PUT of a *opaquelocktoken:* 
> resource (cf. apache access log below). I don't know WebDAV in detail to 
> know what's going wrong here but the colon in the resource name looks 
> suspicious as it's not a permitted character under Windows. Could this 
> indeed be a problem of not escaping the resource name properly?

Could you try a recent 'next'? We had a fix there which should solve your problem, too.

Ciao, Dscho

← back to recent threads