From owner-freebsd-ports@FreeBSD.ORG Wed Jun 15 13:32:00 2005 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22F3A16A41C for ; Wed, 15 Jun 2005 13:32:00 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from jengal.datamax.bg (jengal.datamax.bg [82.103.104.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB29243D53 for ; Wed, 15 Jun 2005 13:31:59 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from sinanica.bg.datamax (sinanica.bg.datamax [192.168.10.1]) by jengal.datamax.bg (Postfix) with QMQP id 761F187CD; Wed, 15 Jun 2005 16:31:58 +0300 (EEST) Received: (nullmailer pid 56835 invoked by uid 1004); Wed, 15 Jun 2005 13:31:58 -0000 Date: Wed, 15 Jun 2005 16:31:58 +0300 From: Vasil Dimov To: "Loren M\. Lang" Message-ID: <20050615133158.GB50642@sinanica.bg.datamax> References: <20050615052417.GA27969@alzatex.com> <20050615062637.GA28464@alzatex.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <20050615062637.GA28464@alzatex.com> X-OS: FreeBSD 5.4-STABLE User-Agent: Mutt/1.5.9i Cc: freebsd-ports@freebsd.org Subject: Re: Download URL for blobwars. X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vd@datamax.bg List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2005 13:32:00 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Jun 14, 2005 at 11:26:37PM -0700, Loren M. Lang wrote: > On Tue, Jun 14, 2005 at 10:24:17PM -0700, Loren M. Lang wrote: ... > > PORTNAME and DISTVERSION as appropriate. This caused fetch to grab the > > file successfully, but it saved it as > > > > download.php?type=zip&file=blobwars-1.04-1.tar.gz > > > > instead of blobwars-1.04-1.tar.gz so extract then fails. Though when I ... > I think what's happening here is that libfetch doesn't understand the > Content-disposition header that the site is sending out and so is saving > the file with the wrong name. The fix would be to add support for the > content-disposition header to libfetch or use a suitable replacement > that understands the header. The only other alternative I can see it to This would be quite insecure, imagine that server requests the file to be saved as ../../../../../../etc/passwd or ~/.profile or something else unexpected. You should use -o ${KNOWNFILENAME} as Roman Neuhauser suggests. -----BEGIN PGP SIGNATURE----- iD8DBQFCsC3OFw6SP/bBpCARAq4wAJ9ZuhQ+tHaP1t3wD0s3sb8j+0MWJQCg2rlP ipmWRE6+fu593YmYUQbfOW0= =Lbqg -----END PGP SIGNATURE-----