WGET has used proxies for agest. Set the http_proxy environment variable e.g. in bash for our proxy on 10.10.1.1 port 3128 http_proxy=http://10.10.1.1:3128 and do ftp for good measure ftp_proxy=ftp://10.10.1.1:3128 then you need to export the settings export http_proxy export ftp_proxy I think that's how I sorted it. Rob At 14:02 16/06/2003 +0100, you wrote:
The plot thickens.. seems theres already a 1.7.1 version of it on SuSE, yet i have compiled 1.8.1 to *somewhere*
I found a configuration file stashed away in the usr/local portion of the system. I uncommented the necessary lines - i spotted the additional http_address line that isn't displayed in the options of the wget binary.
Its possible it was an addition to the program since 1.7.x
--- Simon Kelsall <simon@kelsall.net> wrote: > On Mon, 16 Jun 2003 12:17:56 +0100 (BST), you wrote:
Anyway we are sat behind a proxy that is on port 80 but at a specific address, and wget decides just to aim itself at port 80 on our local box. :/
I think Wget supports the http-proxy environment variable ?
-- Simon Kelsall.
Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://uk.messenger.yahoo.com/
-- To unsubscribe, e-mail: suse-linux-uk-schools-unsubscribe@suse.com For additional commands, e-mail: suse-linux-uk-schools-help@suse.com