Dan Kalowsky wrote:
>
> Hello,
>
> I'm trying to implement a "friendly" error page. Where in the case of
> receiving an HTTP 404 (for example) error for a page, having the browser
> redirect the user to what a marketing person has decided is more helpful
> screen.
Oh, no. What happens if that page 404s or there's a network error? What
happens if the user actually understands what's going on and this
confuses? Will it mess up their history?
IE's "friendly" error pages are the most annoying thing, particularly for
tech support people:
"I can't access this page!"
"What does it say?"
"It says I can't access the page, and I should try reloading, and..."
"No, which error is it?"
"An 'I can't access this page' error"
"No, the number hidden in really tiny letters at the bottom"
"Oh."
<five minutes later>
"404 error".
"Right! The website is broken."
"Oh, is that all?"
"Yes. <sigh>"
Gerv
