Comment 62 for bug 186920

Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 186920] Re: bzr xmlrpc client doesn't use http proxy, causing network errors trying to resolve lp: urls

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tim wrote:
> Hello,
> now it finally works when I issue:
>
> SET HTTP_PROXY=proxy.example.com:8000
> SET HTTPS_PROXY=proxy.example.com:8000
> bzr co -Dhttp nosmart+http://code.launchpad.net/~flavour/sahana-eden/trunk
>
> on the Windows command line.
>
> Should be documented like this.
>
> I still regard this nosmart and etc. stuff as overhead.
>
> Why not bzr co lp:mycode?
>

My guess is that your proxy is refusing a POST request, which is sort of
silly. (The final target would refuse it, and we would fall back
gracefully to the regular code paths.)

Also, I'm not sure what version of bzr you are using, but bzr 2.2
introduced support for using lp: behind proxies. (It is a long-standing
bug that the xmlrpc library that is built into python doesn't support
http proxies.)

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxlmOIACgkQJdeBCYSNAAMbHgCgxJrb5JaiBEnChpkQnu5a4mK2
C38AoKiIePIkGz6KA6AwV1B9FcjfbddK
=5LF1
-----END PGP SIGNATURE-----