What steps will reproduce the problem?
1. export http_proxy=http://10.0.2.2:3128
2. export https_proxy=""
3. Run pulledpork -vv and lo-and-behold: MY HTTPS PROXY is copied from
http_proxy?
What is the expected output? What do you see instead?
I expected HTTPS PROXY to be empty, as done just before running pulledpork. Do
note however that the HTTPS PROXY reported by pulledpork *is not* used. My
environment does require me to specify a https_proxy, and because I left it
empty, nothing is being downloaded. The reported MY HTTPS PROXY is simply wrong.
What version of the product are you using? On what operating system?
Pulledpork 0.7.0, Debian 7.7
Please provide any additional information below.
.
Original issue reported on code.google.com by jaccovan...@gmail.com on 7 May 2015 at 9:49
Original issue reported on code.google.com by
jaccovan...@gmail.com
on 7 May 2015 at 9:49