bzr 2.5.0 - Problem with https+webdav

[Andreas Sommer]

Hi,

since I updated from 2.5b1 to 2.5b6 (now I'm reporting this problem with
the stable version 2.5.0), I'm having problems when trying to push using
password-protected https+webdav (on Apache with mod_dav).

I always get the following output. This is on Windows, and note that I
disable certificate checking because I have a self-signed certificate
and didn't yet read up about recent changes in Bazaar regarding that:

Working tree "C:/path/to/repo/" has uncommitted changes (See bzr
status). Uncommitted changes will not be pushed.
Using saved push location:
https+webdav://myhostname.dyndns.org/bzr/repositoryname/
Not checking SSL certificate for myhostname.dyndns.org: 443
HTTPS myhostname.dyndns.org, Realm: 'some realm name' username: myusername
HTTPS myusername at myhostname.dyndns.org, Realm: 'some realm name' password:
Not checking SSL certificate for myhostname.dyndns.org: 443
Not checking SSL certificate for myhostname.dyndns.org: 443
Not checking SSL certificate for myhostname.dyndns.org: 443
Not checking SSL certificate for myhostname.dyndns.org: 443
bzr: ERROR: Invalid http response for
https://myhostname.dyndns.org/bzr/repositoryname/.bzr/repository/upload/yhldic2a8qeuzq76wpof.pack:
Unable to handle http code 400: Bad Request

Looking into my Apache log, the problem seems to be a PUT statement
(guess it's the .pack file upload?!):

[...] - myusername [10/Mar/2012:21:24:20 +0100] "PUT
/bzr/repositoryname/.bzr/repository/upload/yhldic2a8qeuzq76wpof.pack
HTTP/1.1" 400 522 "-" "bzr/2.5.0 (urllib)"

Any ideas? (Does anyone else use webdav?)

Note that I patched the webdav module to work with bzr 2.5 - was just a
missing function parameter, so that cannot cause the problem:
https://code.launchpad.net/~andidog/bzr-webdav/trunk
<https://code.launchpad.net/%7Eandidog/bzr-webdav/trunk>

Best regards,
 Andreas Sommer