So, the only thing as far as launchpad is concerned that uses https is the resolution of lp: urls via the xmlrpc server. Giving launchpad your ssh public key and setting your launchpad username in bzr avoids the issue as bzr+ssh is used instead of http. Passing '-Ossl.cert_reqs=none' just for the initial branch operation also works, as bzr remembers the resolved http url for future operations.
Steps to reproduce:
* Install tinyproxy, which comes up on localhost:8888 in default configuration
* Run a command through the proxy with no launchpad_username set, against a lp: branch:
$ BZR_HOME=/tmp HTTPS_PROXY=http://localhost:8888 bzr info lp:bzr
bzr: ERROR: Certificate error: hostname 'localhost' doesn't match either of '*.launchpad.net', 'launchpad.net'
* The safe effect can be had with other hosts and protocols, so it seems to be general issue with proxying:
So, the only thing as far as launchpad is concerned that uses https is the resolution of lp: urls via the xmlrpc server. Giving launchpad your ssh public key and setting your launchpad username in bzr avoids the issue as bzr+ssh is used instead of http. Passing '-Ossl. cert_reqs= none' just for the initial branch operation also works, as bzr remembers the resolved http url for future operations.
Steps to reproduce:
* Install tinyproxy, which comes up on localhost:8888 in default configuration
* Run a command through the proxy with no launchpad_username set, against a lp: branch:
$ BZR_HOME=/tmp HTTPS_PROXY=http:// localhost: 8888 bzr info lp:bzr
bzr: ERROR: Certificate error: hostname 'localhost' doesn't match either of '*.launchpad.net', 'launchpad.net'
* The safe effect can be had with other hosts and protocols, so it seems to be general issue with proxying:
$ HTTPS_PROXY=http:// localhost: 8888 bzr info https:/ /github. com/paramiko/ paramiko. git
bzr: ERROR: Certificate error: hostname 'localhost' doesn't match either of 'github.com', 'www.github.com'