Date: Tue, 04 Mar 2003 11:11:21 -0500 From: "Brian J. McGovern" <bmcgover@cisco.com> To: Dag-Erling Smorgrav <des@ofug.org> Cc: "Brian J. McGovern" <bmcgover@cisco.com>, qa@freebsd.org, bmcgover@bmcgover-pc.cisco.com Subject: Re: Changes to libfetch in 5.0 break proxy support? Message-ID: <200303041611.h24GBLae005394@bmcgover-pc.cisco.com> In-Reply-To: Your message of "Tue, 04 Mar 2003 17:04:09 %2B0100." <xzpel5n2k5i.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
> "Brian J. McGovern" <bmcgover@cisco.com> writes: > > Here you go. This is done from a bash shell, having run a > > export FETCH_BEFORE_ARGS=-vvv > > export HTTP_PROXY=proxy-host.cisco.com:80 > > export FTP_PASSIVE_MODE=YES > > >From what you've shown me, I can only conclude that libfetch is > performing as expected, and the proxy is broken. > > You can try to work around it by setting FTP_PROXY to an empty string, > which would tell libfetch not to use a proxy for FTP downloads. > Unfortunately, I need the proxy to get out of our restricted lab network. > > The hostnames have been altered to protect my internal network :) In this > > example, the proxy is running FreeBSD 5.0 with the stock apache 1.3 from > > the ports. The config file was edited so that proxy module was enabled. > > Verification of proxy was done by setting mozilla to use it for HTTP and > > FTP proxy, and several web pages and ftp transfers were done. Similarly, s ome > > 4.7 clients were used with the last two of the three enviornment variables > > set (above), and it worked. > > Please show me the output of a successful download with the same > options. > Will do, but it will probably be tomorrow, as I'm at home today, and don't have a handy 4.7 box to use that isn't in use for its normal business function. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200303041611.h24GBLae005394>