From owner-freebsd-ports Thu Mar 15 14:56:12 2001 Delivered-To: freebsd-ports@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id D25A737B718 for ; Thu, 15 Mar 2001 14:56:08 -0800 (PST) (envelope-from babolo@links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id BAA19385; Fri, 16 Mar 2001 01:55:18 +0300 (MSK) Message-Id: <200103152255.BAA19385@aaz.links.ru> Subject: Re: curl 7.6.1 port : HTTP proxy not working In-Reply-To: from "Dag-Erling Smorgrav" at "Mar 10, 1 06:34:13 pm" To: des@thinksec.com (Dag-Erling Smorgrav) Date: Fri, 16 Mar 2001 01:55:18 +0300 (MSK) Cc: roam@orbitel.bg, Stephane.Lentz@ansf.alcatel.fr, ports@FreeBSD.ORG From: .@babolo.ru MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dag-Erling Smorgrav writes: > Peter Pentchev writes: > > > I don't think this counts as 'much more powerful', but curl sure does > > have some strong points (whereas fetch(1) unarguably has others :) > > I was actually hoping to hear something like "curl can fetch this file > but fetch(1) can't" so that I could sit down with the code for an hour > or two and then answer back "it can now" :) > I don't know if curl can, but fetch as many others can't get http://www.fortunecity.es/consola/gorilas/408/120301/Mikegunn.gif http://www.fortunecity.es/consola/gorilas/408/120301/Thor.zip The first looks as a fortunecity logo until cookies sent. The second redirects to some text/html until cookies sent. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message