On Tue, Feb 17, 2009 at 4:43 PM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
> Marc G. Fournier wrote:
>> On Tue, 17 Feb 2009, Alvaro Herrera wrote:
>
>>> Yes. It has been fixed and broken several times in the past. I think
>>> this is on Marc's court; my guess is that it breaks every time Apache is
>>> upgraded on that server.
>>
>> That makes zero sense, but let's deal with the issue vs "yet another"
>> haphazard guess at the cause ...
>
> Let's just say I'm happy you fixed it, and I hope it won't break again.
Surely the correct fix is to do an http level permanent redirect (301)
to anoncvs.postgresql.org, rather than maintain both servers.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
