Re: Wget (was Chrome and Safari IP leak)

["Geoff Down" <geoffdown@xxxxxxxxxxxx>]

On Tue, 07 Dec 2010 15:34 -0800, "Mike Perry" <mikeperry@xxxxxxxxxx>
wrote:

> Turns out that wget can be 302d between schemes to cause you to bypass
> proxy settings. For example, if you have the $HTTP_PROXY environment
> variable set but nothing for $HTTPS_PROXY, a 302 to an https url will
> cause you to bypass proxy. I wouldn't be surprised if the same could
> happen for an ftp url.
> 

Interesting. If I have in .wgetrc
 https_proxy = http://127.0.0.1:8118
redirection still fails:

 wget -O - https://paypal.com/
--00:27:52--  https://paypal.com/
           => `-'
Resolving 127.0.0.1... 127.0.0.1
Connecting to 127.0.0.1:8118... connected.
Proxy request sent, awaiting response... 301 Moved Permanently
Location: https://www.paypal.comhttps://paypal.com/ [following]

Is that a PayPal problem or a Wget problem?

GD

-- 
http://www.fastmail.fm - Choose from over 50 domains or use your own

***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxxx with
unsubscribe or-talk    in the body. http://archives.seul.org/or/talk/