Yvon Kephren wrote:
In Mozilla there is no 404 error page. There is just an alert that
states the url of the document cannot be found and the page remains
blank or keeps the content previously on the screen.
My problem is not in Internet Explorer, Souly in Mozilla there is an
alert that I would like to avoid.
The way to avoid the alert is to have your server not generate 404 HTTP
responses. This is what the original reply to your post is saying.
The way to avoid sending 404 HTTP responses is to have your server
redirect to a 404 error page (handler) so that a 404 is never actually
sent to the browser.
Beyond that, there's little you can do to avoid a dialog box appearing
in a particular user agent at the application level. Client-side
Javascript simply can't do anything about the browser receiving, and
acting on, a 404 HTTP response. However, from my testing Firefox 0.9
does not show an "alert()" style dialog unless the host _can't be found_
(resolved). If it receives a 404 HTTP response, it displays "The
specified page was not found at <host>."
Regardless, there's nothing you can do about an application level dialog
appearing when Firefox/Mozilla can't resolve a hostname using
client-side Javascript.
--
| Grant Wagner <gw*****@agricoreunited.com>
* Client-side Javascript and Netscape 4 DOM Reference available at:
*
http://devedge.netscape.com/library/...ce/frames.html
* Internet Explorer DOM Reference available at:
*
http://msdn.microsoft.com/workshop/a...ence_entry.asp
* Netscape 6/7 DOM Reference available at:
*
http://www.mozilla.org/docs/dom/domref/
* Tips for upgrading JavaScript for Netscape 7 / Mozilla
*
http://www.mozilla.org/docs/web-deve...upgrade_2.html 
