Re: [pgsql-advocacy] Gborg: announcement by 404

From: Michael Paesold <mpaesold(at)gmx(dot)at>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-advocacy(at)postgresql(dot)org, pgsql-www(at)postgresql(dot)org
Subject: Re: [pgsql-advocacy] Gborg: announcement by 404
Date: 2007-11-14 08:15:29
Message-ID: 473AAEA1.9080300@gmx.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-www

Gregory Stark wrote:
> "Greg Sabino Mullane" <greg(at)turnstep(dot)com> writes:
...
>> http://gborg.postgresql.org/project/slony1
>>
>> ...which now gives a very unfriendly 404 message from pgfoundry. Granted,
>> the first Google hit is the authoritative one, but this is probably
>> just the tip of the dead link iceberg. Google on 'pljava', 'dbdpg',
>> or 'pgsphere' for some even scarier examples.
>
> I think the problem here is that if there's an error Google will notice that
> and stop returning search results. If there's a page saying "I'm not a page"
> then Google will assume that's what's supposed to be there.

That's what redirection using "301 Moved Permanently" is for. It will tell
Google that the new page permanently replaced the old one. Concerning
Google, this is a better solution than either a 404 or a human-readable
page about the move.

Best Regards
Michael Paesold

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Magnus Hagander 2007-11-14 08:50:25 Re: [pgsql-advocacy] Gborg: announcement by 404
Previous Message Gregory Stark 2007-11-14 08:02:14 Re: Gborg: announcement by 404

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2007-11-14 08:50:25 Re: [pgsql-advocacy] Gborg: announcement by 404
Previous Message Gregory Stark 2007-11-14 08:02:14 Re: Gborg: announcement by 404