> 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?
