Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date:	Fri, 28 Apr 2000 12:38:53 -0400
Message-Id:	<200004281638.MAA05417@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to:	<20000428121527.C1614@cygnus.com> (message from Chris Faylor on
	Fri, 28 Apr 2000 12:15:27 -0400)
Subject:	Re: [greenbaum AT ti DOT com: cygwin setup and firewalls]
References:	<200004281415 DOT KAA14347 AT delorie DOT com> <200004281558 DOT LAA05110 AT envy DOT delorie DOT com> <20000428121527 DOT C1614 AT cygnus DOT com>

> As I keep repeatedly saying, I have looked into a couple of these
> "proxy issues" and they were only problems with parsing of the ftp
> data being returned.  I've fixed this when I can.

If setup can't get the initial HTTP file, it's not an ftp issue.
That's the spot to note proxy instructions.

- Raw text -