Search this site:


February 21, 2005 12:13 AM

Broken: Page-not-found error

RestartCarina Zona writes:

This has to be the worst page-not-found error ever.  First, it's a news site which has already expired an article that's only 5 days old.  It doesn't even offer the option of registering or paying to see the article. Instead of display a standard error message or a user-friendly explanation, it spits out this startling request to "restart site".

Closer inspection of the page only yields another baffling clue: the title "HTML/OS  Restart Page" implies that not only the web server will be restarted but a whole operating system!  Bizarre.


Well, the "HTML/OS" bit comes because the product that's serving up that page is called "Aestiva HTML/OS" - .

But it is an odd error page, yeah. :D

Posted by: Ciaran at February 21, 2005 05:18 AM

A major failing in the behaviour of many web based systems is the direction of error messages as output. For the most part, the person using a web page has no ability to really do anything with an error. These types of errors ought to be directed to a standard error output log. Aside from "Page Not Found" errors, I've seen many VBscript failures, and database failures sent back as response pages. Completely inappropriate for most circumstances.

Posted by: Carlos Gomez at February 21, 2005 07:24 AM

Just curious, was the "Restart Site" a link that you could click on? If so, did it "restart site"? What a fun way to mess with the organization! Just randomly restart their site whenever you feel like!

Posted by: Ray at February 21, 2005 07:29 AM

If you click on the linked word "This" above you will go directly to the error page. Clicking the link goes to the page's homepage; it does not appear to actually restart the server (though that would be fun).

Basically, though, this is very poor customer service. There's little reason for them to make articles completely unavailable after just 5 days.

Posted by: Jay at February 21, 2005 08:59 AM

Unless they put so many articles up that they ran out of server space after only 5 days.

Posted by: fuzzy at February 21, 2005 10:21 AM

I have restarted the site, so you may want to wait a few minutes for it to come back up. ;D

Broken, oh soooooo broken.

Posted by: Joshua Wood at February 21, 2005 03:24 PM

Maybe we should give them a call and tell them we just restarted their website. I'd like to see what kind of reaction I'd get.

Posted by: Jay at February 22, 2005 08:59 AM

Reaction: "What?! Hacker!! Hacker!! I'm calling the police. Turn our website back on!"

Posted by: Brian at February 23, 2005 11:09 AM

Then they press the power button on their server to turn their website back on and end up turning it off.

Posted by: fuzzy at February 23, 2005 05:45 PM


Posted by: mo at March 22, 2005 07:27 PM

The article is probably available after 5 days. The page is not available anymore, because of the number in the url: that is a session number, which is expired. Like the first poster said, it's made with HTML/OS, and there is an easy way to fix things like this.... (and yes, I'm an HTML/OS programmer).. so that you can read that article again, even when the link has been expired...

Posted by: johan at April 7, 2005 04:27 PM

They fixed it. Now it says:

We're sorry, but the page you requested is no longer available.

Please use the site search or archive search to locate the article.

Return to previous page

Posted by: Andrew at May 23, 2005 05:47 PM

Comments on this entry are closed

Previous Posts: