[issue2599] qclone fails from behind an http proxy

[Kamil Kisiel]

New submission from Kamil Kisiel <kamil at kamilkisiel.net>:

For a repository that works via a regular clone:

$ hg clone https://kisielk@bitbucket.org/kisielk/mercurial-reviewboard-mq r1
requesting all changes
adding changesets
adding manifests
adding file changes
added 175 changesets with 381 changes to 113 files (+2 heads)
updating to branch default
50 files updated, 0 files merged, 0 files removed, 0 files unresolved

the qclone of the same repo fails:

$ hg qclone --debug https://kisielk@bitbucket.org/kisielk/mercurial-
reviewboard-mq r2
using https://bitbucket.org/kisielk/mercurial-reviewboard-mq
proxying through http://proxy.lan.zymeworks.com:3128
http auth: user kisielk, password not set
sending between command
using https://bitbucket.org/kisielk/mercurial-reviewboard-mq/.hg/patches
http auth: user kisielk, password not set
sending between command
abort: error: Connection refused

I verified that the qclone of the same repo works from a machine not behind 
the proxy. The evidence leads me to believe this is a bug in MQ.

I also tested this with a repository on my personal webserver that uses 
plain HTTP instead of HTTPS and it fails with the same error. It looks like 
the problem is not limited to the HTTPS protocol.

----------
messages: 14967
nosy: kisielk
priority: bug
status: unread
title: qclone fails from behind an http proxy

____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue2599>
____________________________________________________