bzr 2.5.0 - Problem with https+webdav

[Andreas Sommer]

From: Vincent Ladeuil <vila+bzr at canonical.com>Sent: 12.03.2012 18:10
To: Andreas Sommer <andreas.sommer87 at googlemail.com>
Cc: bazaar at lists.canonical.com
Subject: Re: bzr 2.5.0 - Problem with https+webdav
>>>>>> Andreas Sommer <andreas.sommer87 at googlemail.com> writes:
> 
>     > 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:
> 
> Can you retry the same command with the -Dhttp debug parameter added ?
> 
> It's probably best to file a bug to track the issue so you can attach
> the relevant part of the .bzr.log file (where -Dhttp will output more
> info), 'bzr version' will tell you where the .bzr.log file is on your
> machine.

Okay, should I file a bug in bzr-webdav or in bzr? As webdav uses bzr's
urllib wrappers, I think it should go into bzr.


>     > 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?)
> 
> Did you upgrade anything else than bzr itself, did you have a working
> setup before that, is there some unusual pattern regarding the access
> rights for the files/dirs there ?
> 
> '400' is the error code for 'Bad Request'... could it be that somehow
> the webdav server part is configured in such a way that it's not enabled
> there ?
> 
> Are you may be pushing to a new path where webdav is not configured ?

I have a setup that worked perfectly fine between bzr 2.0 and 2.5b1.

>     > 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>
> 
> I've commented there, thanks for that.

Thanks for having a look.

>      Vincent