From owner-freebsd-ports Fri Mar 9 9:56:27 2001 Delivered-To: freebsd-ports@freebsd.org Received: from aes.thinksec.com (aes.thinksec.com [193.212.248.16]) by hub.freebsd.org (Postfix) with ESMTP id A7B9237B719 for ; Fri, 9 Mar 2001 09:56:24 -0800 (PST) (envelope-from des@thinksec.com) Received: (from des@localhost) by aes.thinksec.com (8.11.3/8.11.3) id f29HuLH49625; Fri, 9 Mar 2001 18:56:21 +0100 (CET) (envelope-from des@thinksec.com) X-Authentication-Warning: aes.thinksec.com: des set sender to des@thinksec.com using -f X-URL: http://www.ofug.org/~des/ To: Stephane.Lentz@ansf.alcatel.fr Cc: ports@FreeBSD.ORG Subject: Re: curl 7.6.1 port : HTTP proxy not working References: <20010309152555.A25496@nickfury.netfr.alcatel.fr> From: Dag-Erling Smorgrav Date: 09 Mar 2001 18:56:18 +0100 In-Reply-To: Stephane Lentz's message of "Fri, 9 Mar 2001 15:25:55 +0000" Message-ID: Lines: 15 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Stephane Lentz writes: > I wanted to use the curl package to grab packages, sources & so on > through our corporate proxy (curl is much powerfull than fetch). What, specifically, does curl do that fetch(1) doesn't? I don't want a laundry list, I just want to know what features fetch(1) lacks that you personally need. > I found out that the curl package does not support HTTP proxy. Fetch(1) does. DES --=20 Dag-Erling Sm=F8rgrav - des@thinksec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message