Allow folloing 302 codes in FETCH_ARGS in bsd.port.mk

[Matthias Andree]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 19.07.2010 23:30, schrieb Doug Barton:
> On Sun, 18 Jul 2010, Baptiste Daroussin wrote:
> 
>> Hi,
>>
>> What about removing the -A option from FETCH_ARGS to allow fetch to
>> follow 302 code.
> 
> I've always wondered why we have that in the defaults, perhaps someone
> who knows can answer? If it served a valid purpose in the past, but does
> not any longer, perhaps it's time to remove it?

The default is there because some web servers redirect to other sites
(mirrors) with some 30X code, rather than reporting 404 - as documented
in my fetch(1) manual page :-)

I think I have quite recently seen this on SourceForge.

At least if we remove that flag, we need to make sure fetch isn't fooled
into an unterminated loop of redirects. Such as: redirect to actual
address and more than a dozen redirects would abort and fail the fetch.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (FreeBSD)

iEYEARECAAYFAkxEyjoACgkQvmGDOQUufZX4ZQCfdDMxAH7XP40gorZu0BDX9Ak4
8xIAn3wlxOgSkjZqOtOM45sAWEs7ohuD
=jz/w
-----END PGP SIGNATURE-----