svn http/https transport

[Jelmer Vernooij]

Hi Ricardo,

Ricardo Kirkner wrote:>
> I've been working with a branch of an svn backed project that is
> exported through https. I stumbled upon a problem with bzr interacting
> with the http authentication.
> 
> There are actually two issues:
> 
> 1. When no username is provided in the url, I get an error about 'Unable
> to handle http code 401: Authorization Required'
This issue is also in the bug tracker as bug 256612. I've
(coincidentally) posted a patch to the list earlier this week, which
will make Bazaar prompt if there is no username it knows it can use:

http://bundlebuggy.aaronbentley.com/project/bzr/request/%3C20090331142523.17D6857B84%40charis.vernstok.nl.vernstok.nl%3E

> 2. When the username is passed through in the URL, I always get prompted
> for the password
> 
> Now, the svn credentials are supposed to be used, because I have them
> stored in the svn credentials store, but that is not happening.

bzr-svn contains a authentication credentials provider that can retrieve
credentials from ~/.subversion. However, given the way the
authentication settings in Bazaar work at the moment, you have to
explicitly specify that Bazaar should use the Subversion credentials
provider for a particular host, I think something like:

[host1]
host = host
password_encoding = subversion

It would of course be nice if Bazaar could always see if there are
credentials in the Subversion cache that apply rather than requiring
this redirect, see https://bugs.edge.launchpad.net/bzr/+bug/321918 for
details. With this bug fixed, there should be no need to register
bzr-svn's Transport class as the primary http transport (which also
breaks all non-svn http operations).

Cheers,

Jelmer