From owner-freebsd-ports@FreeBSD.ORG Tue Jan 11 11:24:17 2005 Return-Path: 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 12F0B16A4CE for ; Tue, 11 Jan 2005 11:24:17 +0000 (GMT) Received: from eskimo.tundraware.com (eskimo.tundraware.com [64.2.229.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DB8E43D53 for ; Tue, 11 Jan 2005 11:24:14 +0000 (GMT) (envelope-from tundra@tundraware.com) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by eskimo.tundraware.com (8.13.1/8.13.1) with ESMTP id j0BBOBfu019591 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Tue, 11 Jan 2005 05:24:11 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <41E3B75B.4030203@tundraware.com> Date: Tue, 11 Jan 2005 05:24:11 -0600 From: Tim Daneliuk Organization: TundraWare Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-ports@freebsd.org X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner: Found to be clean X-MailScanner-From: tundra@tundraware.com Subject: Ports Retrieval And https X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: tundra@tundraware.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2005 11:24:17 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have recently migrated the site that hosts my FreeBSD ports from http to https - I automatically redirect the http requests to the equivalent https URL. This seems to have broken all my ports which now report that the files have been 'Moved Temporarily'. Changing the master site entry to use https instead of http seems to fix this problem. So, I guess the question is - is there some simple way to fix this without having to resubmit each of the ports in question. Interestingly, a command line 'fetch' to the http://... URL seems to work fine. Ideas? - -- - ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFB47dayjgA+Mact+YRAqpBAJ9HYaWY/bSmJ25MSqPV+ZftcZODDACeOJXC TMC+vqcMrOu9xN/EEnI3fXQ= =Xvce -----END PGP SIGNATURE-----