From owner-freebsd-ports  Tue Oct 21 17:38:19 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id RAA21924
          for ports-outgoing; Tue, 21 Oct 1997 17:38:19 -0700 (PDT)
          (envelope-from owner-freebsd-ports)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA21916;
          Tue, 21 Oct 1997 17:38:08 -0700 (PDT)
          (envelope-from fenner@parc.xerox.com)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <56251(5)>; Tue, 21 Oct 1997 17:37:11 PDT
Received: by crevenia.parc.xerox.com id <177487>; Tue, 21 Oct 1997 17:36:57 -0700
From: Bill Fenner <fenner@parc.xerox.com>
To: fenner@freebsd.org, itojun@itojun.org
Subject: Re: FreeBSD ports: 1 unfetchable distfiles: sysutils/mei
Cc: ports@freebsd.org
Message-Id: <97Oct21.173657pdt.177487@crevenia.parc.xerox.com>
Date: Tue, 21 Oct 1997 17:36:51 PDT
Sender: owner-freebsd-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Yuck.  I explicitly flag HTTP redirections as being unfetchable, under
the assumption that the only reason for an HTTP redirect is to point
to the new canonical location, and the old canonical location will be
going away soon.

Now that there's some history parsing in the results script, the
checking script can check the redirected-to URL and log it, and if
in the future the original site goes away, the redirected URL will
have been logged in the history.

  Bill