From: | "Selena Deckelmann" <selenamarie(at)gmail(dot)com> |
---|---|
To: | "Dave Page" <dpage(at)pgadmin(dot)org> |
Cc: | "PostgreSQL WWW" <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: broken links (intermittent) |
Date: | 2008-09-30 14:36:49 |
Message-ID: | 2b5e566d0809300736h16631fm99fa122678f9abaa@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Tue, Sep 30, 2008 at 7:10 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> On Tue, Sep 30, 2008 at 3:00 PM, Selena Deckelmann
> <selenamarie(at)gmail(dot)com> wrote:
>
> > Could we put a more informative 404 message in place? A contextual one
> would
> > be ideal. In this case, we could serve a "not found" page with a
> suggestion
> > to check out the backups portion of the documentation.
> >
> > Or, maybe in this specific case there should just be a redirect to the
> top
> > of the backups-related docs.
>
> Not easily, if at all. The documentation is dynamically generated from
> a database on the master server, which certainly doesn't know what
> pages might have been present in previous releases, at least without
> trawling through them all and trying to figure it out.
>
> The frontend servers that you actually get the pages from are all
> static servers that just serve the pre-generated HTML. They have no
> way of dynamically generating a 404 page.
Ok. Can we at least put up a static 404 error page?
I have one mocked up, attached.
--
Selena Deckelmann
PDXPUG - http://pugs.postgresql.org/pdx
Me - http://www.chesnok.com/daily
Attachment | Content-Type | Size |
---|---|---|
404.html | text/html | 5.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Chander Ganesan | 2008-09-30 14:52:59 | Finding some bug statistics.. |
Previous Message | David Fetter | 2008-09-30 14:32:51 | Re: pgsql-ports retirement party was [PORTS] libpq windows 64bit support |