Date: Wed, 22 Apr 1998 20:40:01 -0700 (PDT) From: Dave Chapeskie <dchapes@ddm.on.ca> To: freebsd-bugs Subject: Re: bin/6371: fetch(1) uses HTTP_PROXY for ftp requests when FTP_PROXY undefined Message-ID: <199804230340.UAA19999@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/6371; it has been noted by GNATS. From: Dave Chapeskie <dchapes@ddm.on.ca> To: Martin Cracauer <cracauer@cons.org> Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/6371: fetch(1) uses HTTP_PROXY for ftp requests when FTP_PROXY undefined Date: Wed, 22 Apr 1998 23:36:37 -0400 On Wed, Apr 22, 1998 at 12:32:45PM +0200, Martin Cracauer wrote: > Theres are the cases to consider: [...] > 3) I have a proxy that uses the http protocol and serves http and ftp > requests. That means, you can get ftp urls by using http to talk to > your proxy. This is what fetch does when HTTP_PROXY is set, but > FTP_PROXY isn't. > > You fix breaks case 3, which is a pretty common one, IMHO. I at > least use such a proxy. It doesn't break it. Just don't set FTP_PROXY. All I did was change the meaning of FTP_PROXY="" from undefined to "Don't use any proxy". > What we need here is a standard for $..._PROXY environment variables > that allows us to control the protocol and the kind of url seperatly, > preferrably without breaking older clients. Yes! But until that comes along... Wow, all this discussion about a three line work around. I suppose that's a good thing so that mis-features don't get into the tree. If indeed this is a mis-feature then by all means let it die. However, I have yet to be convinced. -- Dave Chapeskie <dchapes@ddm.on.ca>, DDM Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199804230340.UAA19999>